On Wed, 2011-11-16 at 15:34 -0800, mrdiesel wrote: > I got the segmentation fault again. but i was able to process 4000 messages. > before it was crapping right away. there must be a leak somewhere else? > right? > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/The-Decaf-Threading-API-is-in-a-Shutdown-State-Exception-tp4077689p4078311.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hard to say, still don't know what version of the library you have, make sure you have the latest v3.4.0. The only way to debug is to capture a backtrace of all the threads at the time of the segfault. You know you don't need to create a connection / session etc each time you want to consume a message right? You can just create a consumer and call receive when you want a message. Regards -- Tim Bish ------------ FuseSource Email: tim.b...@fusesource.com Web: http://fusesource.com Twitter: tabish121 Blog: http://timbish.blogspot.com/
