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: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <27065498.post@talk.nabble.com>
Date: Thu, 7 Jan 2010 11:19:23 -0800 (PST)
From: zdvickery <zach.vickery@sensus.com>
To: users@activemq.apache.org
Subject: Re: ExceptionListener behavior in Connection class and NMS 1.2.0
In-Reply-To: <1262891312.2444.4.camel@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <27026733.post@talk.nabble.com>
 <1262730801.2320.13.camel@localhost> <27065051.post@talk.nabble.com>
 <1262891312.2444.4.camel@localhost>


Timothy Bish wrote:
> 
> If you think you've found an issue then by all means open a new Jira
> issue.  We'd need a good description of the problem along with steps to
> reproduce it and a sample app that demonstrates the problem if
> possible.  
> 
> When you say the TCP connect is getting closed reset, who exactly is
> closing / resetting the connection?
> 
> Regards
> Tim.
> 

The issue in my mind is to understand "what is the correct behavior of these
events?" and then to ensure the library meets the specification.  Right now,
what these events do seems to predicated on the use of failover transport,
whether it is associated with a publisher or subscriber, and the NMS
version.  It's more of a specification effort than anything; I'm not sure if
that's what you want logged in Jira.

As far as the connection is concerned, there are two scenarios which seem to
produce identical behavior in the NMS library.  I haven't sniffed them to
determine if they are being closed with a FIN or RST:
- ActiveMQ is restarted
- SSH tunnel used for transport is closed
-- 
View this message in context: http://old.nabble.com/ExceptionListener-behavior-in-Connection-class-and-NMS-1.2.0-tp27026733p27065498.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.