On Wed, 2011-08-24 at 08:51 -0700, urciolo wrote: > We do have producer flow control enabled. However, we were not at that > limit. Attached is another stack trace from a linux client. This is on a > different box, but attached to the same broker as the first stack trace I > sent (cleaner stack trace). The snip below shows onException. Did something > happen that caused a deadlock during a transport failure? > > #15 0x404c387f in activemq::transport::failover::CloseTransportsTask::add () > #16 0x404d00c5 in > activemq::transport::failover::FailoverTransport::handleTransportFailure () > from /usr/local/lib/libactivemq-cpp.so.14 > #17 0x404e18cf in > activemq::transport::failover::FailoverTransportListener::onException () from > /usr/local/lib/libactivemq-cpp.so.14 > #18 0x404a0b51 in activemq::transport::TransportFilter::fire () > #19 0x404a0b94 in activemq::transport::TransportFilter::onException () > #20 0x404a0b51 in activemq::transport::TransportFilter::fire () > #21 0x404a0b94 in activemq::transport::TransportFilter::onException () > #22 0x404e2b9e in > activemq::transport::inactivity::InactivityMonitor::onException () from > /usr/local/lib/libactivemq-cpp.so.14 > #23 0x404a0b51 in activemq::transport::TransportFilter::fire () > #24 0x404a0b94 in activemq::transport::TransportFilter::onException () > #25 0x4049e38f in activemq::transport::IOTransport::fire () > #26 0x4049ec9b in activemq::transport::IOTransport::run () >
I beleive this is the same issue as reported here: https://issues.apache.org/jira/browse/AMQCPP-376 Regards -- Tim Bish ------------ FuseSource Email: tim.b...@fusesource.com Web: http://fusesource.com Twitter: tabish121 Blog: http://timbish.blogspot.com/
