[JBoss JIRA] Created: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
8:55 a.m.
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it may manually reconnect to another node of
the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:51 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
[
https://issues.jboss.org/browse/JBMESSAGING-1855?page=com.atlassian.jira....
]
Justin Bertram updated JBMESSAGING-1855:
----------------------------------------
Description: If the cluster node to which a client is connected is dropped gracefully
and the cluster is using FailoverOnNodeLeave = false then the client's connection will
die and its exception listener will not be triggered so it will never have a chance to
manually reconnect to another node of the cluster. (was: If the cluster node to which a
client is connected is dropped gracefully and the cluster is using FailoverOnNodeLeave =
false then the client's connection will die and its exception listener will not be
triggered so it may manually reconnect to another node of the cluster.)
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it will never have a chance to manually
reconnect to another node of the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:45 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
[
https://issues.jboss.org/browse/JBMESSAGING-1855?page=com.atlassian.jira....
]
Yong Hao Gao commented on JBMESSAGING-1855:
-------------------------------------------
The root cause is that the client (MDB) receives messages from JBM server via
JBossConnectionConsumer. When at a moment no messages arrive it uses
MessageConsumer.receive(0)
to block and wait for any new messages. If now the connected node failed (shutdown
normally) and the cluster's failoverOnNodeLeave is false, the client will finally
failed to fail over and will notify the client's registered listener after clean up.
However the clean up work requires all ongoing invocations to have finished before closing
the JMS resources. Because there is a receive() call stay there, the clean up will wait
for it to returns. As long as the receive(0) blocks there, the clean up cannot proceed and
therefore the listener will never be notified.
One thing to be noted is that the receive(0) call is not directly reading from socket.
Rather it waits on a lock. When messages come in asynchronously it will get notified. So
the connection broken doesn't make this call returns.
To fix this, I plan to add a notification to the consumer in such a case. When failover
fails, it first notifies any consumers blocked on receive(0), letting it return so the
failover can go on to clean up and notify client's listeners if any.
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it will never have a chance to manually
reconnect to another node of the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:01 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
[
https://issues.jboss.org/browse/JBMESSAGING-1855?page=com.atlassian.jira....
]
Yong Hao Gao closed JBMESSAGING-1855.
-------------------------------------
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it will never have a chance to manually
reconnect to another node of the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:01 p.m.
New subject: [JBoss JIRA] Resolved: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
[
https://issues.jboss.org/browse/JBMESSAGING-1855?page=com.atlassian.jira....
]
Yong Hao Gao resolved JBMESSAGING-1855.
---------------------------------------
Resolution: Done
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it will never have a chance to manually
reconnect to another node of the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:50 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
[
https://issues.jboss.org/browse/JBMESSAGING-1855?page=com.atlassian.jira....
]
Justin Bertram commented on JBMESSAGING-1855:
---------------------------------------------
I don't see a "Fix Version" for this, Howard. Do you know what version
it's in?
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it will never have a chance to manually
reconnect to another node of the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:58 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
[
https://issues.jboss.org/browse/JBMESSAGING-1855?page=com.atlassian.jira....
]
Justin Bertram commented on JBMESSAGING-1855:
---------------------------------------------
Looking at the revision numbers, it looks like this went into 1.4.0.SP3.CP12. Do you
agree?
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it will never have a chance to manually
reconnect to another node of the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:58 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
[
https://issues.jboss.org/browse/JBMESSAGING-1855?page=com.atlassian.jira....
]
Yong Hao Gao commented on JBMESSAGING-1855:
-------------------------------------------
doh!
I see the commit log is Apr 6 2011. So the earliest releases that include this fix is
JBoss Messaging 1.4.8.GA (29 Apr 2011)
JBoss Messaging 1.4.0.SP3_CP12 (29 Apr 2011)
Howard
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it will never have a chance to manually
reconnect to another node of the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9 a.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
[
https://issues.jboss.org/browse/JBMESSAGING-1855?page=com.atlassian.jira....
]
Yong Hao Gao reopened JBMESSAGING-1855:
---------------------------------------
update versions
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it will never have a chance to manually
reconnect to another node of the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:02 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
[
https://issues.jboss.org/browse/JBMESSAGING-1855?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1855:
--------------------------------------
Fix Version/s: 1.4.8.GA
1.4.0.SP3.CP12
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP12, 1.4.8.GA
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it will never have a chance to manually
reconnect to another node of the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:02 a.m.
New subject: [JBoss JIRA] Resolved: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
[
https://issues.jboss.org/browse/JBMESSAGING-1855?page=com.atlassian.jira....
]
Yong Hao Gao resolved JBMESSAGING-1855.
---------------------------------------
Resolution: Done
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
Fix For: 1.4.8.GA, 1.4.0.SP3.CP12
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it will never have a chance to manually
reconnect to another node of the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:02 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
[
https://issues.jboss.org/browse/JBMESSAGING-1855?page=com.atlassian.jira....
]
Yong Hao Gao closed JBMESSAGING-1855.
-------------------------------------
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP12, 1.4.8.GA
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it will never have a chance to manually
reconnect to another node of the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:08 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener
[
https://issues.jboss.org/browse/JBMESSAGING-1855?page=com.atlassian.jira....
]
Yong Hao Gao commented on JBMESSAGING-1855:
-------------------------------------------
Yeah I agree. :)
Thanks
Failed fail-over doesn't trigger client's ExceptionListener
-----------------------------------------------------------
Key: JBMESSAGING-1855
URL: https://issues.jboss.org/browse/JBMESSAGING-1855
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP09
Reporter: Justin Bertram
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP12, 1.4.8.GA
If the cluster node to which a client is connected is dropped gracefully and the cluster
is using FailoverOnNodeLeave = false then the client's connection will die and its
exception listener will not be triggered so it will never have a chance to manually
reconnect to another node of the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4756
days inactive
4943
days old
12 comments
2 participants
participants (2)
-
Justin Bertram (JIRA) -
Yong Hao Gao (JIRA)