Nevermind, i came across the solution when i wrote the sample code. The problem was caused by my internal thread handling, and is now solved. Works like a charm now, plus i got 2.1.1 now :)
Thanks for your help. Mittler, Nathan wrote: > > Why don't you create an issue > http://issues.apache.org/activemq/browse/AMQCPP and attach and example > application that illustrates the problem. > > Nate > >> -----Original Message----- >> From: pfid [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, November 13, 2007 8:41 AM >> To: users@activemq.apache.org >> Subject: Re: Amq client crash when losing connection to broker >> >> >> >> tabish121 wrote: >> > >> > Please upgrade to ActiveMQ-CPP 2.1.1 as this sounds like an >> error that >> > we fixed. Then let us know if it still misbehaves. >> > >> > Regards >> > Tim >> > >> >> Still doesnt work. >> I should mention though, that my test client uses 2 activemq >> queues at the moment. The first one can be closed/deleted >> without any problems, the second queue will hang at >> >> if (connection) >> { >> connection->stop(); >> connection->close(); // ---> here <--- >> } >> >> or at "delete connection;" respectively when i skip the close >> part, stop() will work though. Each queue runs in a seperate >> thread with their own activemq session/connection/.. objects. >> >> By the way, if i open some queue with a wrong (unknown) host, >> e.getMessage().c_str() returns "Success". >> >> try >> { >> // open activemq queue >> } >> catch (CMSException& e) >> { >> e.getMessage().c_str() >> } >> -- >> View this message in context: >> http://www.nabble.com/Amq-client-crash-when-losing-connection- >> to-broker-tf4792112s2354.html#a13726015 >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Amq-client-crash-when-losing-connection-to-broker-tf4792112s2354.html#a13741705 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
