Hi
I'm working on a http connector and get a rather big json from the device with a channel configuration and status. In a QAction this json is parsed into an object, but sometimes the json string is cut short. I did a wireshark capture and saw something called "Continuation" after some of the get requests.
Not sure this is the root cause of the problem.
I hoped that when the next time the QAction was triggered the remaining part of the json string was retrieved, but I got the beginning of the next channel json instead.
I've tried to replicate the issue with postman and there I sometimes get a Timeout.
Hi Arne, what's the timeout time that is currently configured on the element? Maybe try to increase that value, to see if that solves the problem.
If it does, you could use <Session ignoreTimeout=""> or <Session timeout=""> to either don't use a timeout or increase it only for that particular session.
The continuation packets that you see in WireShark normally don't cause problems. It means that the data was too big to send in one packet and was split in multiple packets. DataMiner combines these packets again before setting the parameter.
Hi I tried increasing it to 20s from the original 1.5s, but eventually I did receive a cutoff json again.
The DataMiner version 10.2.12.0-12434-CU1