Bug Agent triggers the events twice

[HHeermann]

We had a problem with agent that triggers the payloads twice. You can see below sample requests and logs

curl -X PUT
http://194.219.31.157:9997/agent/remote/objects/e5c654dd-788d-4e0c-aaf2-5836aa9f1139/properties/prop
-H ‘Content-Type: application/json’
-H ‘adapter-id: b8:27:eb:51:7d:9a’
-H ‘cache-control: no-cache’
-H ‘infrastructure-id: b8:27:eb:51:7d:9a#3070’
-d ‘{
“userId”: “”,
“adapterId”: “b8:27:eb:51:7d:9a”,
“deviceId”: “b8:27:eb:51:7d:9a#3070”,
“deviceType”: “PANIC-BUTTON”,
“dateRecorded”: “2018-12-11 15:23:14”,
“client”: “raspberry”,
“properties”:
[
{
“code”: “event_type”,
“unit”: “string”,
“value”: “PanicBtn”
}
],
“ehpProperties”: null
}’

ec 12, 2018 3:47:33 PM org.restlet.security.ChallengeAuthenticator authenticate
WARNING: Authentication failed. No verifier provided.
Dec 12, 2018 3:47:33 PM org.restlet.security.ChallengeAuthenticator authenticate
WARNING: Authentication failed. No verifier provided.
Dec 12, 2018 3:47:33 PM org.restlet.engine.log.LogFilter afterHandle
INFO: 2018-12-12 15:47:33 127.0.0.1 - - 9997 PUT /agent/objects/e5c654dd-788d-4e0c-aaf2-5836aa9f1139/properties/prop sourceOid=dcd8379c-9369-426f-b823-066c8eb4719a 200 12 260 10 http://localhost:9997 Restlet-Framework/2.3.9 -
Dec 12, 2018 3:47:33 PM org.restlet.security.ChallengeAuthenticator authenticate
WARNING: Authentication failed. No verifier provided.
Dec 12, 2018 3:47:33 PM org.restlet.engine.log.LogFilter afterHandle
INFO: 2018-12-12 15:47:33 127.0.0.1 - - 9997 PUT /agent/objects/e5c654dd-788d-4e0c-aaf2-5836aa9f1139/properties/prop sourceOid=dcd8379c-9369-426f-b823-066c8eb4719a 200 12 260 8 http://localhost:9997 Restlet-Framework/2.3.9 -
Dec 12, 2018 3:47:34 PM org.restlet.engine.log.LogFilter afterHandle
INFO: 2018-12-12 15:47:34 192.168.1.217 - - 9997 PUT /agent/remote/objects/e5c654dd-788d-4e0c-aaf2-5836aa9f1139/properties/prop - 200 81 260 177 http://194.219.31.157:9997 PostmanRuntime/7.4.0 -

We resolved the issue after installing the last version. I had one before from 11/11/2018I don’t know if is the version that solved the problem, or the issue appears after some other conditions