Parsing issue

Hi Anton,

On a fresh Traccar 3.17 installation with a default configuration (incl. H2 DB), but with event forwarding enabled, I witnessed a parsing error.
I attached the whole session log in case it was caused by some previous messages. The parsing error happens at 2018-06-09 05:53:16 where it only properly reads the device ID but the rest is wrong.

The invalid parsing result:

2018-06-09 05:53:16 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2447100088850553150906184730762102012183144e000000efe7fbffff001b540000003d00e801ff1e0000000504
2018-06-09 05:53:16  INFO: [630C7F67] id: 4710008885, time: 2000-01-03 04:03:45, lat: 0.08387, lon: -100.14808, speed: 531.0, course: 509.0

I can see in the log that before and after, the device sent pretty much the same message and Traccar was able to parse it properly. So why did it get this one wrong?

Could this be related to this issue: https://www.traccar.org/forums/topic/traccar-3-7-odd-position-issue/

The whole session log:

2018-06-09 05:41:28 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2a48512c343731303030383838352c56312c3136333334392c562c303030302e303030302c4e2c30303030302e303030302c452c3030302e30302c3030302c3035303631382c46464646464246462c3233322c30312c666636342c302c3623
2018-06-09 05:41:28  INFO: [630C7F67] id: 4710008885, time: 2018-06-05 16:33:49, lat: 0.00000, lon: 0.00000, course: 0.0
2018-06-09 05:41:47 DEBUG: [630C7F67: 5013 > 77.218.240.191] HEX: 2a48512c3030302c56342c5337312c3038353930322c313823
2018-06-09 05:41:50 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2a48512c343731303030383838352c56342c5337312c3038353930322c313831384c4b5f4341525f5451323031382f30342f31392031383a30392c69642c343731303030383838352c49503a31382e3138342e3139372e3133303a353031332c73312c6d326d2e74656c65322e636f6d2c2c2c5332362c533030
2018-06-09 05:44:28 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2a48512c343731303030383838352c56312c3136333634392c562c303030302e303030302c4e2c30303030302e303030302c452c3030302e30302c3030302c3035303631382c46464646464246462c3233322c30312c666636342c302c3623
2018-06-09 05:44:28  INFO: [630C7F67] id: 4710008885, time: 2018-06-05 16:36:49, lat: 0.00000, lon: 0.00000, course: 0.0, result: S71,085902,1818LK_CAR_TQ2018/04/19 18:09,id,4710008885,IP:18.184.197.130:5013,s1,m2m.tele2.com,,,S26,S00*HQ,4710008885,V1
2018-06-09 05:47:22 DEBUG: [630C7F67: 5013 > 77.218.240.191] HEX: 2a48512c3030302c5337312c3038353930322c32322c313023
2018-06-09 05:47:22  INFO: user: 2, action: edit, object: device, id: 6
2018-06-09 05:47:28 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2a48512c343731303030383838352c56312c3136333934392c562c303030302e303030302c4e2c30303030302e303030302c452c3030302e30302c3030302c3035303631382c46464646464246462c3233322c30312c666636342c302c3623
2018-06-09 05:47:28  INFO: [630C7F67] id: 4710008885, time: 2018-06-05 16:39:49, lat: 0.00000, lon: 0.00000, course: 0.0
2018-06-09 05:47:28 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2a48512c343731303030383838352c56342c5337312c3038353930322c3232
2018-06-09 05:47:54 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2447100088851640160506180000000006000000000c000000fffffbffff001b000000003d00e801ff640000007700
2018-06-09 05:50:28 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2a48512c343731303030383838352c56312c3136343234392c562c303030302e303030302c4e2c30303030302e303030302c452c3030302e30302c3030302c3035303631382c46464646464246462c3233322c30312c666636342c302c3623
2018-06-09 05:50:28  INFO: [630C7F67] id: 4710008885, time: 2018-06-05 16:42:49, lat: 0.00000, lon: 0.00000, course: 0.0, result: S71,085902,22$G��@
                                                                                                                                                    �������dw*HQ,4710008885,V1
2018-06-09 05:50:39 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2447100088851643010506180000000003000000000c000000efe7fbffff0019000000003d00e801ff310000000601
2018-06-09 05:50:39  INFO: [630C7F67] id: 4710008885, time: 2018-06-05 16:43:01, lat: 0.00000, lon: 0.00000, course: 0.0
2018-06-09 05:51:21 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2447100088851643430506180000000003000000000c000000efe7fbffff001b000000003d00e801ff2b0000000502
2018-06-09 05:51:21  INFO: [630C7F67] id: 4710008885, time: 2018-06-05 16:43:43, lat: 0.00000, lon: 0.00000, course: 0.0
2018-06-09 05:52:06 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2447100088850552050906184730762103012183144e000000efe7fbffff0018240000003d00e801ff280000000503
2018-06-09 05:52:06  INFO: [630C7F67] id: 4710008885, time: 2018-06-09 05:52:05, lat: 47.51270, lon: 12.30524, course: 0.0
2018-06-09 05:53:16 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2447100088850553150906184730762102012183144e000000efe7fbffff001b540000003d00e801ff1e0000000504
2018-06-09 05:53:16  INFO: [630C7F67] id: 4710008885, time: 2000-01-03 04:03:45, lat: 0.08387, lon: -100.14808, speed: 531.0, course: 509.0
2018-06-09 05:53:28 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2a48512c343731303030383838352c56312c3035353332362c412c343733302e373632312c4e2c30313231382e333134342c452c3030302e30302c3030302c3039303631382c45464537464246462c3233322c30312c666631652c302c3223
2018-06-09 05:53:28  INFO: [630C7F67] id: 4710008885, time: 2018-06-09 05:53:26, lat: 47.51270, lon: 12.30524, course: 0.0
2018-06-09 05:54:16 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2447100088850554150906184730762102012183144e000000efe7fbffff0016340000003d00e801ff1e0000000505
2018-06-09 05:54:16  INFO: [630C7F67] id: 4710008885, time: 2018-06-09 05:54:15, lat: 47.51270, lon: 12.30524, course: 0.0
2018-06-09 05:55:09 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2447100088850555080906184730760003012183270e000000fffffbffff001a340000003d00e801ff340000007506
2018-06-09 05:55:09  INFO: [630C7F67] id: 4710008885, time: 2018-06-09 05:55:08, lat: 47.51267, lon: 12.30545, course: 0.0
2018-06-09 05:56:28 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2a48512c343731303030383838352c56312c3035353632362c412c343733302e373630302c4e2c30313231382e333237302c452c3030302e30302c3030302c3039303631382c46464646464246462c3233322c30312c666636342c302c3623
2018-06-09 05:56:28  INFO: [630C7F67] id: 4710008885, time: 2018-06-09 05:56:26, lat: 47.51267, lon: 12.30545, course: 0.0
2018-06-09 05:57:08 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2447100088850557070906184730760006012183270e000000fffffbffff001e540000003d00e801ff640000007707
2018-06-09 05:57:08  INFO: [630C7F67] id: 4710008885, time: 2018-06-09 05:57:07, lat: 47.51267, lon: 12.30545, course: 0.0
2018-06-09 05:59:28 DEBUG: [630C7F67: 5013 < 77.218.240.191] HEX: 2a48512c343731303030383838352c56312c3035353932362c412c343733302e373630302c4e2c30313231382e333237302c452c3030302e30302c3030302c3039303631382c46464646464246462c3233322c30312c666636342c302c3623
2018-06-09 05:59:28  INFO: [630C7F67] id: 4710008885, time: 2018-06-09 05:59:26, lat: 47.51267, lon: 12.30545, course: 0.0

Yes, it's likely the same issue.

Reading the thread I thought it was fixed in 3.8 and the workaround is not required anymore.

So limiting message length should be enough?

<entry key='h02.messageLength'>45</entry>

Or do I have to disable LBS too?

Message length in your case is 47.