500 error from vex server when uploading data

[radumas]

Using the initial release jar along
with the csv-uploader release jar.

When I try to upload data I get, in the csv-uploader terminal, 0 records uploading and in the traffic-engine-app terminal the following:

Received response code 500 from vex server
Sep 09, 2015 5:31:55 PM com.conveyal.traffic.app.engine.EngineWorker run
WARNING: Index: 0, Size: 0
Sep 09, 2015 5:31:55 PM com.conveyal.traffic.osm.OSMDataStore loadOSMTile
INFO: loading osm from: http://osm.conveyal.com/vex/?n=-22.917922936146038&s=-23.079731762449885&e=-43.41796875&w=-43.59375

repeated over and over again with slightly different coordinates. The application.conf file is the one that's currently present in this repository.

[kpwebb]

Ah, yeah, I see what's happened here. Looks like there's a mismatch in how Vex is being called. We updated the Vex API and it looks like this is still using the old API signature. I'm guessing one of the components is just out of date in Maven.

I'll investigate and post a fix in the AM. Thanks!

[radumas]

Ah understood. Thanks!

[kpwebb]

@radumas can you just drop the the "/vex" suffix from the application.conf file? Line should read:

application.vex=http://osm.conveyal.com

This will point you back to the older version of vex while we update the Maven repo.

Note that this works
http://osm.conveyal.com/?n=-22.917922936146038&s=-23.079731762449885&e=-43.41796875&w=-43.59375

while this does not:

http://osm.conveyal.com/vex/?n=-22.917922936146038&s=-23.079731762449885&e=-43.41796875&w=-43.59375

[radumas]

OK thanks. I'll try this Monday and let you know if I succeed.

[radumas]

Worked!

[radumas]

Hi @kpwebb , just wondering if this workaround was still necessary.

[linux-devil]

INFO: loading osm from: http://osm.conveyal.com/?n=13.068776734357701&s=12.897489183755889&e=77.51953125&w=77.34375
Received response code 502 from vex server