Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <11658208.post@talk.nabble.com>
Date: Tue, 17 Jul 2007 14:33:30 -0700 (PDT)
From: brahn <brahn@firstam.com>
To: users@activemq.apache.org
Subject: Re: ActiveMQ : java.lang.OutOfMemoryError: unable to create new
 native thread
In-Reply-To: <11657559.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <11656339.post@talk.nabble.com>
 <73FD1BFF-5BB4-4B0C-B79A-F0DABCE84BCC@gmail.com>
 <11657296.post@talk.nabble.com> <11657559.post@talk.nabble.com>


We had this problem as well.  We resolved it by sending a DISCONNECT command
before our stomp client quits.    If you don't send the DISCONNECT command,
the connections will continue to add up in ActiveMQ until it crashes with
the error you got.  This behavior seems to have started with ActiveMQ 4.1,
since we didn't have this problem with older versions.


-- 
View this message in context: http://www.nabble.com/ActiveMQ-%3A-java.lang.OutOfMemoryError%3A-unable-to-create-new-native-thread-tf4099069s2354.html#a11658208
Sent from the ActiveMQ - User mailing list archive at Nabble.com.