Guys,
I've been using QPID successfully for a few months now, however once
in a while my program terminates with this exception:
terminate called after throwing an instance of
'qpid::framing::SessionBusyException'
what(): session-busy: Channel 3 attached to
guest.50e08be0-d1f6-4c43-8b81-cd782838d6be (qpid/client/ConnectionImpl.cpp:98)
terminate called after throwing an instance of
'qpid::framing::SessionBusyException'
what(): session-busy: Channel 2 attached to
guest.b2a5593f-6692-425d-a0a4-f123bb679935 (qpid/client/ConnectionImpl.cpp:98)
I'm sure I'm doing something wrong here, can anyone point me in the
right direction?
My application works as follows.
One FailoverManager.
failoverManager->execute( ... );
is called from different threads, no mutex here.
I have two flavors of FailoverManager::Commands that are passed to
the FailOverManager:
1. Sending single Topic messages. (These happen all the time from
different threads)
2. Listening for a list of Topic messages, using the SubscriptionManager
(this list is mutex protected, and typically doesn't change
during runtime of the application unless someone is changing the
configuration, this was not the case during the crashes)
Sadly the minidumps I have are on Linux AMD64 using breakpad, for
which the stack walker is not yet done and hence I can't see where
the crash originated.
Thanks,
Ron
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
