cleanup from the
Consumer Runnable Thread rather than at OnException.
Hope this help any developers who face similar issue.
Regards,
Kok Hoor
--
View this message in context:
http://www.nabble.com/ActiveMQ-CPP-2.0-graceful-cleanup-of-Session-and-Connection-tf3687911s2354.html#a10442566
Sent
t;
>> SxJMSClient.dll!activemq::connector::openwire::OpenWireSessionInfo::~OpenWireSessionInfo()
>>
>> + 0x40 bytes
>>
>> SxJMSClient.dll!activemq::connector::openwire::OpenWireSessionInfo::`scalar
>> deleting destructor'() + 0xf bytes
>>
&
Can you provide sample code that demonstrates the problem?
Kok Hoor wrote:
> Hi,
>
> I am trying to use the ActiveMQ CPP 2.0 library to develop an XPCOM
> component to enable Mozilla XULRunner to use JMS messaging.
>
> However, one problem I face is, when the ActiveMQ Server is down, and
>
:transport::TransportFilter::fire() + 0x54
bytes
SxJMSClient.dll!activemq::transport::TransportFilter::onCommand() +
0x16
bytes
SxJMSClient.dll!activemq::transport::IOTransport::fire() + 0x8a bytes
SxJMSClient.dll!activemq::transport::IOTransport::run() + 0x87 bytes
SxJMSClient.dll!activemq::concurrent::Thread::runCallback() + 0x4f
bytes
msvcr80d.dll!102048d1()
msvcr80d.dll!10204877()
kernel32.dll!7c80b683()
Thanks in advanced.
Regards,
Kok Hoor
--
View this message in context:
http://www.nabble.com/ActiveMQ-CPP-2.0-graceful-cleanup-of-Session-and-Connection-tf3687911s2354.html#a10309769
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
