Issue Regarding L-100 Antlanta Protocol

mail2bishnoi7 years ago

Hi Anton,

When I restart traccar server the following error come -

2017-05-07 11:48:06  INFO: Shutting down server...
2017-05-07 11:48:06  INFO: [D4D986C9] disconnected
2017-05-07 11:48:06  INFO: Operating system name: Linux version: 4.4.0-1016-aws architecture: amd64
2017-05-07 11:48:06  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Oracle Corporation version: 25.121-b13
2017-05-07 11:48:06  INFO: Memory limit heap: 239mb non-heap: 0mb
2017-05-07 11:48:06  INFO: Character encoding: UTF-8 charset: UTF-8
2017-05-07 11:48:06  INFO: Version: 3.10-SNAPSHOT
2017-05-07 11:48:08  WARN: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
 at [Source: <info><status>01111011000001</status><adc1>0</adc1><odometer>485.76</odometer><temp1>50.45</temp1><battery>4</battery><ip>106.215.154.168</ip><distance>0</distance><totalDistance>664.05</totalDistance></info>; line: 1, column: 2] - JsonParseException (... < QueryBuilder:401 < *:451 < DataManager:308 < DeviceManager:65 < ...)
2017-05-07 11:48:09  INFO: Starting server...
2017-05-07 11:48:36  INFO: [DA2A33F4] connected
2017-05-07 11:48:37 DEBUG: [DA2A33F4: 5112 < 106.215.195.80] HEX: 200141544c3836313639333033353238353235332c244750524d432c3036313832372c412c323933352e343233362c4e2c30373335372e363938372c452c302c33352c3037303531372c2c2c2a30312c2330313131313031313030303030312c302c302c302c3438352e37302c35302e33332c342e302c31382c3430342c37302c3136332c3561623641544c0236
2017-05-07 11:48:37  WARN: NullPointerException (DefaultDataHandler:30 < BaseDataHandler:29 < ... < ExtendedObjectDecoder:61 < ...)

Is is ok or we need to change something in our code ?

Anton Tananaev7 years ago

It doesn't look OK. Seems like you have multiple issues. What version of Traccar are you using? Are you using official release without any modifications?

mail2bishnoi7 years ago

Hi Anton,

I am using Traccar3.10 version. I have modified the code for fixing one of the issue related to same protocol.

Anton Tananaev7 years ago

I guess your fix broke something.

mail2bishnoi7 years ago

This issue only come when I restart the server after that its working fine.