Re: [sumo-user] TraCI message length error

[Jakob Erdmann <namdre.sumo@xxxxxxxxx>]

Hello,

this has to do with recent changes to the TraCI protocoll. (see TraCI at http://sumo.dlr.de/wiki/ChangeLog#Other)

When using a development version after [d2c6b60c9b552]

- If you use the python or C++ client you are mostly unaffected

- If you use TraaS, you have to wait for the Maintainer to update the client  (I'm optimistic that he'll have it done for the release next week)

- If you have your own client, you need to patch it as indicated in the changeLog (I can give more details if necessary)

regards,

Jakob

2018-08-27 13:10 GMT+02:00 m.barthauer@xxxxxxxxxxx <m.barthauer@xxxxxxxxxxx>:

Hi,

 

I don't know why but recently my TraCI script stopped working. I am constantly working on it but cannot remember any significant changes with respect to TraCI startup. When executing the first simulation step, SUMO stops because of an unexpected TraCI message length, I presume:

 

Error: tcpip::Storage::readIsSafe: want to read 4 bytes from Storage, but only 3 remaining

 

What reasons can cause this behaviour? Does this have to do with file encoding?

 

Regards

Mirko



_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/sumo-user