BatchUpdate Exception ERROR

[Joshua R Santiago-Ibarra]

Hello: 

I have been trying to run a TransitClockDocker instance. I am using Traccar to get my vehicle locations. For traccar, I understand the implementation in the transitclock.properties is as follows:

transitclock.modules.optionalModulesList=org.transitclock.custom.traccar.TraccarAVLModule;org.transitclock.core.schedBasedPreds.SchedBasedPredsModule

transitclock.avl.traccar.email= email

transitclock.avl.traccar.password= password

transitclock.avl.traccar.baseurl=http://url/api

I can see that traccar is showing my vehicles. The GTFS file I added to the TransitClockDocker es perfect. There seems to be no visual error.  But transitClock doesn't show them and outputs the following error:

Caused by: java.sql.BatchUpdateException: Batch entry 0 /* insert org.transitclock.db.structs.VehicleState */ insert into VehicleStates (blockId, isDelayed, isForSchedBasedPreds, isLayover, isPredictable, isWaitStop, routeId, routeShortName, schedAdh, schedAdhMsec, schedAdhWithinBounds, tripId, tripShortName, vehicleId, avlTime) values ('R108RT08A', '0', '1', '1', '1', '1', 'R108R', 'Ruta 108 Rural', '0.0 sec (ontime)', 0, '1', 'R108RT08A', 'R108RT08A', 'block_R108RT08A_schedBasedVehicle', '2020-11-13 11:08:27.000000 -04:00:00') was aborted.  Call getNextException to see the cause.

[Joshua R Santiago-Ibarra]

I modified the transitclock.properties and changed the transitclock.modules.optionalModulesList and added 

org.transitclock.custom.traccar.TraccarAVLModule;org.transitclock.core.predAccuracy.PredictionAccuracyModule

But, the vevhicels still don't show 

[Óg Crudden]

Hi Joshua,

Sorry for the late reply. Resending as I forgot to copy to lst.

Just to set your expectation this docker installer is really meant as a guide as to how to install the software, not a perfect installer for all configurations. If you follow the steps in go.sh they show you the main steps.

That said if you commit your config to a fork I can I can try it locally. You would also need to provide me the traccar credentials.

A good place to look for issues is in avl.log and core.log. I suspect your avl may be outside the default min and max latitude values which are set for the US.

Cheers,

Sean.

--
www.thetransitclock.org
---
You received this message because you are subscribed to the Google Groups "TheTransitClock" group.
To unsubscribe from this group and stop receiving emails from it, send an email to thetransitclo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/thetransitclock/aedb3ad8-17f9-483e-a3b3-be50ce396124n%40googlegroups.com.

[Joshua R Santiago-Ibarra]

Hi Sean, 

Thank you for taking your time to answer. I made a dork with the code I'm using. It already has the GTFS url and traccar implementation. The following link is my fork repo:

https://github.com/jSantiago318/transitclockDocker/tree/MPK

Thank you  for the help in advance. 

Joshua.

[Joshua R Santiago-Ibarra]

Hi Sean, 

For reference, these are the following errors that show. I checked the core.log and it shows the following error:

Reading WebAgencies data from database "TIM"...

Done reading WebAgencies from database. Took 6 msec. They are [WebAgency [agencyId=1, hostName=127.0.>Done reading WebAgencies from database. Took 9 msec. They are [WebAgency [agencyId=1, hostName=127.0.>Couldn't set RMI timeout to 4 seconds.

java.net.SocketException: factory already defined

The avl.log shows the following:

reading http://url:8082/api/positions

read complete

processed 0 reports for feed http://url:8082/api/positions

[Óg Crudden]

Hi Joshua,

I tried your traccar credentials with this test program and it fails. Could you confirm your traccar credentials by direct mail? It could also be a version issue as the traccar may have been upgraded.  

https://github.com/TheTransitClock/transitime/blob/develop/transitclockTraccarClient/src/main/java/TheTransitClock/transitclockTraccar/GetPositions.java

The server set up is ok but is not getting avl which I think is related to this.

Cheers,

Sean.

To view this discussion on the web visit https://groups.google.com/d/msgid/thetransitclock/dc9e8801-0ae6-43d0-82e8-cbc4d958ecd9n%40googlegroups.com.

[Óg Crudden]

Hi Joshua,

Based on the credentials email you sent I see that the port number is set incorrectly in your properties file. You have it set to 8080 when it would be 8082.

transitclock.avl.traccar.baseurl=http://45.55.84.20:8080/api

When I set it to http://45.55.84.20:8082/api the test program works. 

Cheers,

Sean.

[Joshua R Santiago-Ibarra]

Hi Sean, 

Thank you for all the help, I have transitclock running  now and with predictions.

Best, 

Joshua