Skip to content
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

API did not response! timeout #118

Closed
Bardo-Konrad opened this issue Nov 16, 2013 · 5 comments
Closed

API did not response! timeout #118

Bardo-Konrad opened this issue Nov 16, 2013 · 5 comments

Comments

@Bardo-Konrad
Copy link

I ran

java -Dgraphhopper.config=config-example.properties -Dgraphhopper.osmreader.osm=nordrhein-westfalen-latest.osm.pbf -jar jetty-runner-9.0.4.v20130625.jar --port 8989 graphhopper-web-0.1.1.war

I can open the page.

But once I try to route, it says "API did not response! timeout" after a while even though I routed from frechen to pulheim, which is in nordrhein-westfalen.

How to solve this?

PS: By the way, it's "api did not respond".

@karussell
Copy link
Member

What are the logs telling? Is there an exception or stacktrace?

@Bardo-Konrad
Copy link
Author

Which logs, how do I view them? There's no exception on the screen though. Sehe gerade, wir können auch auf deutsch schreiben.

@karussell
Copy link
Member

the logs where you start the jetty server

@Bardo-Konrad
Copy link
Author

Das ist die Ausgabe:

root@root:/navi# java -Dgraphhopper.config=config-example.properties -Dgraphhopper.osmreader.osm=nordrhein-westfalen-latest.osm.pbf -jar jetty-runner-9.0.4.v20130625.jar --port 42152 graphhopper-web-0.1.1.war
2013-11-16 18:19:57.732:INFO:oejr.Runner:main: Runner
2013-11-16 18:19:58.206:INFO:oejs.Server:main: jetty-9.0.4.v20130625
2013-11-16 18:20:00.713:INFO:oejpw.PlusConfiguration:main: No Transaction manager found - if your webapp requires one, please configure one.
2013-11-16 18:20:09,055 [main] INFO  com.graphhopper.GraphHopper - version 0.1.1|2013-08-06T21:46 (1,2,1,1,1)
2013-11-16 18:20:09,080 [main] INFO  com.graphhopper.GraphHopper - graph LevelGraphStorage|CAR|RAM_STORE|1,2,1,1,1, details:edges:2 587 042(99), nodes:1 206 596(19), name: - (6), geo:6 710 582(26), bounds:5.863066148677457,9.507055048057177,50.30940939432553,52.546079886244534
2013-11-16 18:20:09,080 [main] INFO  graphhopper.http.DefaultModule - loaded graph at:nordrhein-westfalen-latest.osm-gh, source:nordrhein-westfalen-latest.osm.pbf, acceptWay:CAR, class:LevelGraphStorage
2013-11-16 18:20:09,287 [ThreadPool Service Executor] INFO  graphhopper.http.GHThreadPool$1 - ThreadPool Service Executor STARTED
2013-11-16 18:20:09.768:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@791901{/,file:/tmp/jetty-0.0.0.0-42152-graphhopper-web-0.1.1.war-_-any-/webapp/,AVAILABLE}{file:/navi/graphhopper-web-0.1.1.war}
2013-11-16 18:20:09.837:INFO:oejs.ServerConnector:main: Started ServerConnector@1433d17{HTTP/1.1}{0.0.0.0:42152}

Die Logdateien kann ich nicht finden.

GraphHopper API offline? http://localhost:8989 steht noch auf der Hauptseite

@karussell
Copy link
Member

If you change the port you'll need to change this in the javascipt too (main.js) or use the latest master where this is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants