Hi @TomF > ,
Yes, it seems to me the broker is closing the connection as well, but I do not know the real reason for it. The error shows up right after the set of log messages below:
SDK INFO Thu Nov 24 08:16:34.687 2022 solClientSocket.c:136 (7f0ddd9a2700) Local connection address ‘IP x.x.x.x:45662’ for fd 27, session ‘(c4,s1)_od_fo_prod’
SDK INFO Thu Nov 24 08:16:34.687 2022 solClientSocket.c:685 (7f0ddd9a2700) _solClient_socket_registerForFdEvents, fd 27, events 2, callback ‘0x7f0de7277570’, user data ‘0x7f0dd006d4c0’ for session ‘(c4,s1)_od_fo_prod’
SDK INFO Thu Nov 24 08:16:34.687 2022 solClientSocket.c:764 (7f0ddd9a2700) _solClient_socket_unregisterForFdEvents, fd 27, events 2 for session ‘(c4,s1)_od_fo_prod’
SDK INFO Thu Nov 24 08:16:34.687 2022 solClientSocket.c:685 (7f0ddd9a2700) _solClient_socket_registerForFdEvents, fd 27, events 1, callback ‘0x7f0de7277570’, user data ‘0x7f0dd006d4c0’ for session ‘(c4,s1)_od_fo_prod’
SDK INFO Thu Nov 24 08:16:34.688 2022 solClientOS.c:5758 (7f0ddd9a2700) Peer closed socket, fd 27, cannot read
I have notice when the connection is successfully established at all the following message after the SDK INFO indicating _solClient_socket_registerForFdEvents is the one informing “Information reported by peer for session ‘(c1,s1)_od_fo_prod’: version = ‘9.9.0.23’; date = ‘Apr 29 2021 16:43:20’; platform = ‘Solace PubSub+ 3560’…”.
In the worst scenario I am calling solClient_session_connect() each 15 seconds.
SOLCLIENT_SESSION_PROP_CONNECT_RETRIES is set to “3” and SOLCLIENT_SESSION_PROP_RECONNECT_RETRY_WAIT_MS is set to default value (3000ms). In fact, I have this behavior always after connect to the broker a few times. Seems to me the window of 15 seconds to make the calls is time enough to be able to connect again to the broker. If it is not, do you know what is the minimum wait time between the requests?
Thanks, Tom.