HEX data received, events logged, no positions recorded

Today I discovered a very strange issue - basically the traccar server suddenly stopped recording the positions data from several random devices that had no recent configuration changes. Other devices with the same configuration did not experience this issue.

About the issue - I can see the incoming HEX in the logs, there is the server response but nothing gets recorded in the positions table.

Events like Status unknown or Status Online are being recorded without any issues.

No errors in the logs. Devices use the UDP protocol and "server.instantAcknowledgement" is set to true.

Issue was fixed after traccar service restart.

Any idea what might have gone wrong?

For example:

2024-08-13 00:05:13  INFO: [U976df9ff: teltonika < XX.XX.XX.XX] 0073cafe018e000f3030303030303030303030303030308e01000001913ebff0600002f61a381b7ca9f0000000000000000000000e000700ef0000f00000500000150300c80300450300716400050042316700430ffb0011fff1001200430013ffd900020010031d841001c1000427210000000001
2024-08-13 00:05:13  INFO: [U976df9ff: teltonika > XX.XX.XX.XX] 00050000018e01
2024-08-13 00:05:13  INFO: Event id: 000000000000000, time: 2024-08-13 00:05:13, type: deviceOnline, notifications: 0

Here we can see the Event id but no log that the data is recorded as new position, i.e no log record like the below one:

2024-08-13 00:05:13 INFO: [U976df9ff] id: 000000000000000, time: 2024-08-13 00:05:1, lat: 18.66430, lon: -68.42658, course: 0.0

What version?

Sorry, forgot to mention. It's version 6.1 and I just remembered that I had the same issue back in the day with 5.3. The relevant topic post is here.

Try upgrading to the latest.

Thanks! I am currently testing the latest version but I'm not ready to move it to production yet.

Was this particular issue resolved in the latest version or you are just recommending to use the latest one, hoping the issue will be gone?

Check blog posts.

Is this the one you are referring to: Decouple exception handling?

I can't find another relevant fix. This one deals with UDP but it's for tlt2h protocol, while my devices use teltonika.

https://www.traccar.org/blog/traccar-6-4/

Yes, I saw the blog post and then I turned to check out the Github commits to understand what the "freezing issue" is and how it was fixed. Can you point which commit fixes this freezing issue?

No, but there's a very small number of commits between 6.3 and 6.4, so you should be able to review them all if you're interested in specific code changes.

I checked them all yesterday, most of the 29 commits here are related to various devices protocols and the only two that might have something to do with a "freezing issue" are those:

Decouple exception handling
tlt2h: Fix UDP

Do you mind pointing out at least the commit name or the files that were changed to fix the "freezing issue"?

There were multiple commits. That's why I can't point something specific.

Can you point one of them at least? Or explain what caused the issue?

Since I have no idea what caused this "freezing issue", I cannot say which files had to be changed to fix it either.

https://github.com/traccar/traccar/commit/38cba6d8a21901ff40a3aa1589557ffa9c38d1e8