On Thu, 2010-01-07 at 11:19 -0800, zdvickery wrote:
>
> 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
>
n 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:/
On Thu, 2010-01-07 at 10:52 -0800, zdvickery wrote:
>
> Timothy Bish wrote:
> >
> > I'd need some more information on your setup to give you a definite
> > answer. Are you using the Failover transport? If so then the exception
> > listener is not notified if the connection is dropped, the Failo
ld be good to start with the events and what they should be doing. For
instance, I'm still unclear whether a TCP connection getting closed/reset
should fire a "connection interruped" event or a "connection exception"
event. I can create a bug report for this if de
On Tue, 2010-01-05 at 14:23 -0800, zdvickery wrote:
> I am currently performing some asychronous messaging functionality using
> ActiveMQ/NMS. For various reasons, my process is connected to an ActiveMQ
> server which restarts periodically. I have observed the following behaviors
> with different
shers and
subscribers, yet the ExceptionListener callback is never invoked. I am
curious if this is expected behavior and whether there is anything that can
be done to reliabily detect connection failures?
--
View this message in context:
http://old.nabble.com/ExceptionListener-behavior-in-Conne
