On 22/04/2020 2:57 pm, Toralf Lund wrote:
On 21/04/2020 22:31, Gordon Sim wrote:
How many of the 'Trying to connect' messages are there and how does that compare to the number of stale connections?

At the moment there are 39 connections and 59 connects have been logged, so looks like the connection sometimes goes away. The process has been active since 10 April. I think the connection went away more often in the last version that had a shorter heartbeat interval, but it could be a coincidence.

How many 'timed out' errors do you have in the server logs?

[...]
I wonder if you can close the connections using qpid-tool, and what happens on the client process if you do so?
I have no idea how to do that, I'm afraid. And the qpid-tool "help" command does not really help.

Run qpid-tool with appropriate url to broker. Then type `schema` and repeat until it returns the schema (its not a very polished tool I'm afraid). The do `list connections` and look for one of the stale connections. Then do `call <id> close` where <id> is the connection id of one of the stale connections.

(https://qpid.apache.org/releases/qpid-cpp-1.39.0/cpp-broker/book/chapter-Managing-CPP-Broker.html#MgmtC-2B-2B-Usingqpidtool)

[...]
Connection close will close the TCP socket. If there are active sessions, it will first close those.

I still don't understand. I have 50 connections or whatever, and closing one client socket makes all of them go away?

No, there is a one-to-one relationship between connections and sockets at any time. (A connection that reconnects will create a new socket for the same connection object, but that should only ever happen when the previous socket ended).

Sessions are multiplexed conversations over a connection. There is generally at least one session on a connection, as everything you want to do with a connection requires a session (e.g. send messages, subscribe etc).


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to