Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 marcos.truchado@gmail.com does not designate 216.139.250.139 as permitted
 sender)
Date: Wed, 14 May 2014 11:32:34 -0700 (PDT)
From: mtruchado <marcos.truchado@gmail.com>
To: users@activemq.apache.org
Message-ID: <1400092354694-4681123.post@n4.nabble.com>
In-Reply-To: <1400085818988-4681114.post@n4.nabble.com>
References: <1399623954174-4681005.post@n4.nabble.com>
 <1399664521290-4681006.post@n4.nabble.com>
 <1399664684721-4681007.post@n4.nabble.com>
 <1399974095893-4681082.post@n4.nabble.com>
 <1399975750419-4681083.post@n4.nabble.com>
 <1399977248666-4681084.post@n4.nabble.com>
 <1400085818988-4681114.post@n4.nabble.com>
Subject: Re: activemq-client does not close properly connections to the
 broker
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi

@tabish121: I'm using RedHat AM-Q 6.0 which contains inside AcitveMQ 5.8,
this is a product certificated for production environment, and I'm
evaluating It. ActiveMQ 5.8 is a finalized product that should be stable and
contain the less number of bugs possible. I'm not interested in the trunk.

@artnaseef: this is the guy who triggers the call:

org.jboss.resource.connectionmanager.IdleRemover

It is part of the JBoss EAP 5.2 that we are using. Hmmm, as this is the
trigger of all the evil, maybe It is not an ActiveMQ problem, It is this guy
that triggers the disposal incorrectly, what do you think?

Thanks a lot for your help.


--
View this message in context: http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker-tp4681005p4681123.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.