You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Wes Parish <we...@firstshotprecision.com> on 2010/05/05 00:18:42 UTC
JMS Question
When a connection exception is thrown because of a socket timeout exception, which occurs when a heartbeat times out, it is not being sent to the onException() method. Should this exception be sent like the others to this method?
Wes
Re: JMS Question
Posted by Rajith Attapattu <ra...@gmail.com>.
For the record, I tried with the rpms released under 1.2 and I was
able to get notified via the exception listener when a read timeout
happens.
I am suspecting something else maybe wrong here.
Regards,
Rajith
On Wed, May 5, 2010 at 5:14 PM, Wes Parish <we...@firstshotprecision.com> wrote:
> 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:rajith77@gmail.com]
> Sent: Wed 5/5/2010 3:31 PM
> To: users@qpid.apache.org
> Subject: Re: JMS Question
>
> I ran my test against trunk, however IIRC it should work against 1.2 as well.
> Could you let me know what happens in your situation?
> Does the connection terminate?
>
> Yes, the connection terminates and we fail over to the secondary host. The problem is that we are using dynamic queues through JMS, and after a successful failover, the client application has no way of knowing (without receiving this exception) to re-create the queue on the secondary host.
>
> If so do you get notify via the exception listener? (I assume not
> based on your email) Or is it that you are not getting the right
> exception from the listener?
>
> No, we do not get notified via the exception listener. We do see the exception on stdout.
>
> Rajith
>
> On Wed, May 5, 2010 at 1:55 PM, Wes Parish <we...@firstshotprecision.com> wrote:
>> Rajith,
>>
>> Thank you for the quick reply. We are running Red Hat MRG v1.2 official release. Which version did you run your tests against?
>>
>> Thanks,
>> Wes
>>
>>
>> -----Original Message-----
>> From: Rajith Attapattu [mailto:rajith77@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 "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 than the "read timeout".
>>
>> I think it's more desirable if the "read timeout' exception is thrown
>> rather than the connection closed.
>> (But please note that the "Read Timeout" exception is logged, so
>> information is not lost)
>>
>> On Tue, May 4, 2010 at 6:18 PM, Wes Parish <we...@firstshotprecision.com> wrote:
>>> When a connection exception is thrown because of a socket timeout exception, which occurs when a heartbeat times out, it is not being sent to the onException() method. Should this exception be sent like the others to this method?
>>>
>>> Wes
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Rajith Attapattu
>> Red Hat
>> http://rajith.2rlabs.com/
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:users-subscribe@qpid.apache.org
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:users-subscribe@qpid.apache.org
>>
>
>
>
> --
> Regards,
>
> Rajith Attapattu
> Red Hat
> http://rajith.2rlabs.com/
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
RE: JMS Question
Posted by Wes Parish <we...@firstshotprecision.com>.
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:rajith77@gmail.com]
Sent: Wed 5/5/2010 3:31 PM
To: users@qpid.apache.org
Subject: Re: JMS Question
I ran my test against trunk, however IIRC it should work against 1.2 as well.
Could you let me know what happens in your situation?
Does the connection terminate?
Yes, the connection terminates and we fail over to the secondary host. The problem is that we are using dynamic queues through JMS, and after a successful failover, the client application has no way of knowing (without receiving this exception) to re-create the queue on the secondary host.
If so do you get notify via the exception listener? (I assume not
based on your email) Or is it that you are not getting the right
exception from the listener?
No, we do not get notified via the exception listener. We do see the exception on stdout.
Rajith
On Wed, May 5, 2010 at 1:55 PM, Wes Parish <we...@firstshotprecision.com> wrote:
> Rajith,
>
> Thank you for the quick reply. We are running Red Hat MRG v1.2 official release. Which version did you run your tests against?
>
> Thanks,
> Wes
>
>
> -----Original Message-----
> From: Rajith Attapattu [mailto:rajith77@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 "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 than the "read timeout".
>
> I think it's more desirable if the "read timeout' exception is thrown
> rather than the connection closed.
> (But please note that the "Read Timeout" exception is logged, so
> information is not lost)
>
> On Tue, May 4, 2010 at 6:18 PM, Wes Parish <we...@firstshotprecision.com> wrote:
>> When a connection exception is thrown because of a socket timeout exception, which occurs when a heartbeat times out, it is not being sent to the onException() method. Should this exception be sent like the others to this method?
>>
>> Wes
>>
>
>
>
> --
> Regards,
>
> Rajith Attapattu
> Red Hat
> http://rajith.2rlabs.com/
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: JMS Question
Posted by Rajith Attapattu <ra...@gmail.com>.
I ran my test against trunk, however IIRC it should work against 1.2 as well.
Could you let me know what happens in your situation?
Does the connection terminate?
If so do you get notify via the exception listener? (I assume not
based on your email) Or is it that you are not getting the right
exception from the listener?
Rajith
On Wed, May 5, 2010 at 1:55 PM, Wes Parish <we...@firstshotprecision.com> wrote:
> Rajith,
>
> Thank you for the quick reply. We are running Red Hat MRG v1.2 official release. Which version did you run your tests against?
>
> Thanks,
> Wes
>
>
> -----Original Message-----
> From: Rajith Attapattu [mailto:rajith77@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 "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 than the "read timeout".
>
> I think it's more desirable if the "read timeout' exception is thrown
> rather than the connection closed.
> (But please note that the "Read Timeout" exception is logged, so
> information is not lost)
>
> On Tue, May 4, 2010 at 6:18 PM, Wes Parish <we...@firstshotprecision.com> wrote:
>> When a connection exception is thrown because of a socket timeout exception, which occurs when a heartbeat times out, it is not being sent to the onException() method. Should this exception be sent like the others to this method?
>>
>> Wes
>>
>
>
>
> --
> Regards,
>
> Rajith Attapattu
> Red Hat
> http://rajith.2rlabs.com/
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
RE: JMS Question
Posted by Wes Parish <we...@firstshotprecision.com>.
Rajith,
Thank you for the quick reply. We are running Red Hat MRG v1.2 official release. Which version did you run your tests against?
Thanks,
Wes
-----Original Message-----
From: Rajith Attapattu [mailto:rajith77@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 "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 than the "read timeout".
I think it's more desirable if the "read timeout' exception is thrown
rather than the connection closed.
(But please note that the "Read Timeout" exception is logged, so
information is not lost)
On Tue, May 4, 2010 at 6:18 PM, Wes Parish <we...@firstshotprecision.com> wrote:
> When a connection exception is thrown because of a socket timeout exception, which occurs when a heartbeat times out, it is not being sent to the onException() method. Should this exception be sent like the others to this method?
>
> Wes
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: JMS Question
Posted by Rajith Attapattu <ra...@gmail.com>.
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 than the "read timeout".
I think it's more desirable if the "read timeout' exception is thrown
rather than the connection closed.
(But please note that the "Read Timeout" exception is logged, so
information is not lost)
On Tue, May 4, 2010 at 6:18 PM, Wes Parish <we...@firstshotprecision.com> wrote:
> When a connection exception is thrown because of a socket timeout exception, which occurs when a heartbeat times out, it is not being sent to the onException() method. Should this exception be sent like the others to this method?
>
> Wes
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org