Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of tabish121@gmail.com designates
 209.85.220.171 as permitted sender)
Subject: Re: The Decaf Threading API is in a Shutdown State. Exception
From: Timothy Bish <tabish121@gmail.com>
To: users@activemq.apache.org
In-Reply-To: <1321486444542-4078311.post@n4.nabble.com>
References: <1321473720696-4077689.post@n4.nabble.com>
	 <1321474016.2392.0.camel@OfficePC>
	 <1321475597379-4077794.post@n4.nabble.com>
	 <1321476330.2392.2.camel@OfficePC>
	 <1321476818266-4077852.post@n4.nabble.com>
	 <1321485027.2392.9.camel@OfficePC>
	 <1321485728662-4078288.post@n4.nabble.com>
	 <1321486444542-4078311.post@n4.nabble.com>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 16 Nov 2011 18:38:14 -0500
Message-ID: <1321486694.2392.12.camel@OfficePC>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

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.bish@fusesource.com
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com/