Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Fri, 3 Jan 2014 16:25:29 -0800 (PST)
From: uromahn <ulrich@ulrichromahn.net>
To: users@activemq.apache.org
Message-ID: <1388795129099-4676002.post@n4.nabble.com>
In-Reply-To: <52B72D4B.403@gmail.com>
References: <1387542553266-4675756.post@n4.nabble.com>
 <52B72D4B.403@gmail.com>
Subject: Re: ActiveMQ broker 5.9 doesn't close TCP connection if qpid client
 close amqp connection
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I have seen the exact same behavior.

I have actually initiated the patch for the latest amqp-1-0-client-jms
library. It fixed one issue on the client but the connection still stays
open on ActiveMQ.

According to Rob Godfrey (from the Qpid project) there is a potential issue
in proton-c and also proton-j - the jms client is closing the connection
without detaching from the session and hence the server seems to keep the
connection open for a potential re-connect and resume of the session.

I have not yet tested it with 5.10-SNAPSHOT which is supposed to use a
proton-j-0.6-SNAPSHOT to see if it is fixed there. I can do that during the
next few days and can update this post with my findings.

-Uli


--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-broker-5-9-doesn-t-close-TCP-connection-if-qpid-client-close-amqp-connection-tp4675756p4676002.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.