On 07/11/2012 05:16 AM, Paul Colby wrote:
I don't want to hijack the original topic, but since it //might// be
relevant, the messages I'm seeing are like:
qpidd[32238]: 2012-07-08 23:02:43 error Channel exception: session-busy:
Session already attached:
[email protected](qpid/broker/SessionManager.cpp:55)
qpidd[3435]: 2012-07-08 23:02:43 error Channel exception: session-busy:
Session already attached:
[email protected](qpid/broker/SessionManager.cpp:55)
qpidd[20157]: 2012-07-08 23:02:44 error Channel exception: session-busy:
Session already attached:
[email protected](qpid/broker/SessionManager.cpp:55)
qpidd[32238]: 2012-07-08 23:02:43 error Channel exception: not-attached:
Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:39)
qpidd[3435]: 2012-07-08 23:02:44 error Channel exception: not-attached:
Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:39)
qpidd[20157]: 2012-07-08 23:02:44 error Channel exception: not-attached:
Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:39)
Note, the messages are repeated thrice (each time for a different qpidd
PID), because this is a cluster with three brokers.
That looks like a different issue, an apparent session name clash. I
believe the session name here is made up of the client's host and pid,
along with a counter that is supposed to ensure uniqueness. I don't know
enough about the old QMF console code to suggest the cause, but it does
seem to me to be a bug in that QMF library (or perhaps cumins use of
it). Its probably not terribly harmful; perhaps just a race in a
reconnect or something.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
