the messages get stuck probably on sending - on both sides.
When printed number of received messages (changed the services code to watch some logs) it got stack:
received change requests up to~50% for server, and received up to 30% of responses on client side.
You can catch the exception from socket
[error ] writeMessage Exception: Timeout
this can be handled by setting setSendTimeout for something big (the default is got from os according to poco spec) like 120sec but the socket is stuck anyway, so I don't think it should be changed
Steps To Reproduce
try sending 1000000 long (string over 150characters) messages from client to server. Not all messages will be received by server
Description of the bug
the messages get stuck probably on sending - on both sides. When printed number of received messages (changed the services code to watch some logs) it got stack: received change requests up to~50% for server, and received up to 30% of responses on client side. You can catch the exception from socket [error ] writeMessage Exception: Timeout this can be handled by setting setSendTimeout for something big (the default is got from os according to poco spec) like 120sec but the socket is stuck anyway, so I don't think it should be changed
Steps To Reproduce
try sending 1000000 long (string over 150characters) messages from client to server. Not all messages will be received by server
This affects OLink and MQTT.