On 03/04/2019 09:32, Gordon Sim wrote:
On 03/04/2019 7:32 am, Toralf Lund wrote:
The broker also has a message saying "Connection ... timed out:
closing". This occurs 4-5 seconds after the session-busy error,
according to the timestamps.
So for some reason, the broker is deciding the connection is dead 4-5
seconds after the client has reconnected... what caused the client to
reconnect? Was there a timed out notice there as well?
The direct reason for the reconnect is that "connection::isOpen()"
returns false on a connection that was successfully opened some time in
the past. The connection status is checked periodically. The "reconnect"
option is not set on the connection. Prior to getting a "false"
isOpen(), an exception with message "Failed to connect (reconnect
disabled)" is caught, typically while waiting for incoming messages.
session::nextReceiver() is used for that purpose.
The broker log does not seem to have any messages related to the
original issue.
- Toralf
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
