I've enabled the logging and left the client running during the night.
Hopefully I'll be able to come back to you tomorrow with more details.
The "funny" thing, is that there is no connection lost, we "only" looses the
subscriptions.
I'll try to make a sample tomorrow see if i can reproduce the error

2010/1/25 Timothy Bish <tabish...@gmail.com>

> On Mon, 2010-01-25 at 12:18 +0800, Sebastian Rodriguez wrote:
> > Dear all,
> > I'm encountering a very strange problem.
> > I have a client that uses an embedded broker to connect to a network of
> > brokers.
> > The connection between my client and the embedded broker is done through
> the
> > Apache.NMS.ActiveMQ client.
> > I'm connecting to the embedded broker through a failover uri as I want to
> > recover from possible exception raised.
> > The version of the NMS client is 1.2.0.1794 and we are using the latest
> > version from 5.3.1 branch. This was also happening with the stable
> release
> > 5.3.0.
> >
> > Everything works perfectly until I receive the event
> > ConnectionResumedListener.
> > The weird part is that:
> >
> >    - why do I receive a connection resume event without a previous
> >    connection interrupted event?
> >    - the connection is recovered properly, but not my subscription.
> >    Basically my client doesnt receive anything anymore from the embedded
> broker
> >    although the broker still receives the messages incoming from the
> network of
> >    brokers.
> >
> > Do you have any ideas why I would receive a connection resumed alone
> > (without a connection interrupted?), and why the failover transport
> > correctly recovers the connection but not subscriptions?
> > Thank you very much for your advice on the matter,
> >
>
> Can you enable logging and capture some logs around the time the event
> is fired?  I have not seen any spurious disconnects as yet from NMS.  If
> you have a sample app that can demonstrate the problem that would be
> helpful.
>
> Regards
> Tim.
>
>
>
>
>
>
> --
> Tim Bish
> http://fusesource.com
> http://timbish.blogspot.com/
>
>
>
>


-- 
Sebastien Rodriguez

Reply via email to