have any suggestions that we should try on our side to further
> troubleshoot the problem?
>
> Thanks,
> Wes
>
> -Original Message-
> From: Rajith Attapattu [mailto:rajit...@gmail.com]
> Sent: Wed 5/5/2010 3:31 PM
> To: users@qpid.apache.org
> Subject: Re:
Answers below
Do you have any suggestions that we should try on our side to further
troubleshoot the problem?
Thanks,
Wes
-Original Message-
From: Rajith Attapattu [mailto:rajit...@gmail.com]
Sent: Wed 5/5/2010 3:31 PM
To: users@qpid.apache.org
Subject: Re: JMS Question
I ran my test
al Message-
> From: Rajith Attapattu [mailto:rajit...@gmail.com]
> Sent: Wed 5/5/2010 9:32 AM
> To: users@qpid.apache.org
> Subject: Re: JMS Question
>
> When the socket timeout happens, you do get notified via onException()
> - I just verified this.
> However as soon as the
: JMS Question
When the socket timeout happens, you do get notified via onException()
- I just verified this.
However as soon as the "read timeout" happens the connection is also
closed, and another exception is generated.
Therefore you are most likely to see the "connection aborted&
When the socket timeout happens, you do get notified via onException()
- I just verified this.
However as soon as the "read timeout" happens the connection is also
closed, and another exception is generated.
Therefore you are most likely to see the "connection aborted"
exception from your listener
