-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problems running locally #5
Comments
Alfredo, I will have a look asap. |
Hi, remove comments in the Json config file. |
Hi thank you both. yes I've tested it without the comments of course (I've copy/paste here the wrong version) |
It is a wrong "}" placement : your config should looks like :
|
Hi @serwan thank you for checking: I have already checked the file sent by jsonlint and was ok, but however I've tested again with your version and got the same error, so I suppose it's not a problem in JSON syntax. |
Not realy syntax problem but structural one. The Json config must have 4 entries (title, datasourcetypes, datasources, and prefixes) with the "}" at the wrong place the "prefixies" input was inside datasources. Here is the one I use (with a Blazegraph jnl file)
|
thanks @serwan for the suggestions: I've started editing my file from the example provided in the README, now I've customized a copy of yours and it seems to start. Anyway I still have issues :-(
Moreover in this case the assets (css etc) are missing from the html. thank you in advance for any comment and suggestion. |
If you used the 2.1.0 Blazegraph version to create your jnl file you may activated the geospacial index. Adding "com.bigdata.rdf.store.AbstractTripleStore.geoSpatial":"true" to your Json config (or false if not activated) may fix your error. |
Alfredo, regarding your recent comment with the new issues: Is the version of BlazegraphBasedTPFServer that you are using the one from my github repo here (i.e., https://github.com/hartig/BlazegraphBasedTPFServer) or do you use the version that comes with the official Blazegraph packages? Which version of Blazegraph? Did @serwan's suggestion about adding the 'com.bigdata.rdf.store.AbstractTripleStore.geoSpatial' config option help to solve your problem? (@serwan thanks a lot for your help!) |
Hi Olaf thanks for the reply. 2016-07-04 21:06 GMT+02:00 Olaf Hartig notifications@github.com:
|
Alfredo, can you please pull the latest version from github (
After doing this, you should have two JAR files in the target directory: a small one ( Note that this version of BlazegraphBasedTPFServer in my github repo is using version 2.0.0 of Blazegraph. Once we have fixed your current issues, I can increase the dependency to the most recent version of Blazegraph (2.1.1). |
Hi Olaf thank you very much:I'llcheck tomorrow from work and let you know Il martedì 5 luglio 2016, Olaf Hartig notifications@github.com ha scritto:
Inviato da Gmail Mobile |
Hi @hartig I've done some test, following your directions. 1.) the final shaded.jar gives me some error:
and the error is: I suppose it could be something wrong in the 2.) however the original-shaded.jar file instead works with no errors!
3.) I've trouble finding how to test the url. Testing with requests like:
gives me the error:
I suppose I'm doing something wrong here. Any suggestions? My config.json contains the following properties, inspired from examples:
|
@seralf
Can you try with the latter? Regarding 3: I assume the server is really coming up on port 8080 for you (when starting the server, it should log to the console something like: |
Hi @hartig yes for 1) and 2) the problem it's exactly that. Reading the article you linked I rember I had the same problem in the past in one project, and if I'm not wrong the solution was indeed in explicitly renaming the jar. I wonder if since I'm working on windows platform at the moment, this could be an issue behind the problem (the new shaded.jar should replace the original-shaded.jar, and we know how windows very often causes problems when reading/writing files) For the actual test on the url, I attached a log with only the single request you've requested: it seems that for some reason the context it is not problerly initialized. I had no time to test it from code (for example by unit test), if I will be able I'll post directly some proper test. thank you |
Alfredo, I am not sure what is the bottom line of your response regarding 1 and 2. Can you please confirm that the current version of the pom.xml file works for you without any problems. That is, does your computer generate the two JAR files that I mentioned in my previous mail (and only these)? Or do you have to rename something manually? Regarding the issue for which you attached the log file, it seems that the LDF server does not find a "prefixes" entry in your config file. Can you please verify that this entry is in the file and---also important!---it is in the correct hierarchical position (that is, it is a top-level entry). If it still does not work, please post the current version of your config file here. If it works however, please confirm so that I know it is okay now. |
Sorry for creating confusion @hartig. I confirm that two files are geenrated, as I said earlier. I used the original-shaded.jar while the shaded.jar it's the one with 0 bytes. I was only commenting the article you've cited. For the issues: I'll be able to verify again nex Monday and let you know, thank you for the support. |
Now you are confusing me. Are you sure that you are using the latest version of the pom.xml file? (i.e., the one brought in with the following commit: 96337c4 ? Even with this one you are getting exactly the JAR files mentioned in your earlier comment (#5 (comment))? |
...ahhh ok, finally I got why we were not understand each other, I've missed that update! :-) after updating correctly my local repo with the latest commits, I was able to use the command
to run the server, with the attached once started the server, I tried to call the path any ideas? I've also created a pull request (#6) for UTF-8 configuration support, in order to avoid weird encodings on windows. thank you for the support! |
@seralf The config file that you posted in your recent comment is still having the issue that both @serwan and I have pointed out before (see #5 (comment) and #5 (comment)). I fixed this issue for you in the following file: Please confirm that this is working now for you. |
uhm thankyou both I have to re-check it then! 2016-07-13 18:30 GMT+02:00 Olaf Hartig notifications@github.com:
|
@seralf When you had a chance to test it, please let me know whether it works now. |
Hi Olaf thanks for asking. HTTP ERROR: 503
|
Hi I'm trying to test the server locally and had some issues.
after running:
$ mvn clean package
I've put a
log4j.properties
file and aconfig.json
file in the main directory, then run:I've tried to understand the errors without luck. I attached my configs in case thei could be useful:
config.json
log4j.properties
The text was updated successfully, but these errors were encountered: