[JBoss JIRA] Created: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
2:59 a.m.
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in cluster
and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:01 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=all ]
Tim Fox updated JBMESSAGING-1249:
---------------------------------
JBoss Forum Reference:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4136532#...
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in
cluster and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:42 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=comments#action_1... ]
bodri bodri commented on JBMESSAGING-1249:
------------------------------------------
Note that the consumer is design, so that it survives cluster restarts (it uses the
ExceptionListener).
The actual scenrio is:
1. Starting cluster node0
2. Starting standalone consumer (connected to node0)
3. Starting standalone producer - consumer receives the messages (OK)
4. Starting cluster node1
5. kill cluster node0 (consumer failover transparently on node1)
6. Starting standalone producer - consumer receives the messages (OK)
7. kill cluster node1 - no cluster and no exception callback on the consumer, so it
thinks it is connected (not OK)
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in
cluster and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:45 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=all ]
Andy Taylor reassigned JBMESSAGING-1249:
----------------------------------------
Assignee: Andy Taylor (was: Tim Fox)
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Andy Taylor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in
cluster and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:45 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=comments#action_1... ]
Andy Taylor commented on JBMESSAGING-1249:
------------------------------------------
Ive recreated this using
http://anonsvn.jboss.org/repos/messaging/branches/Branch_JBossMessaging_1....
will investigate further
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Andy Taylor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in
cluster and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:19 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=all ]
Andy Taylor closed JBMESSAGING-1249.
------------------------------------
Fix Version/s: Stable branch
(was: 1.4.1.beta2)
Resolution: Done
The problem was that when fail over occurred and the client reconnected the exception
listener was not being set on the newly created connection. This is now fixed
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Andy Taylor
Fix For: 1.4.0.SP3.CP02, Stable branch
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in
cluster and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:06 p.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=all ]
Clebert Suconic reopened JBMESSAGING-1249:
------------------------------------------
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Andy Taylor
Fix For: 1.4.1.CR1
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in
cluster and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:06 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=all ]
Clebert Suconic updated JBMESSAGING-1249:
-----------------------------------------
Fix Version/s: 1.4.1.CR1
(was: Stable branch)
(was: 1.4.0.SP3.CP02)
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Andy Taylor
Fix For: 1.4.1.CR1
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in
cluster and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:07 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=comments#action_1... ]
Clebert Suconic commented on JBMESSAGING-1249:
----------------------------------------------
Branch_stable version is just a temporary repository of tasks.. please aways put it on a
valid release version before closing a task.
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Andy Taylor
Fix For: 1.4.1.CR1
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in
cluster and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:07 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=all ]
Clebert Suconic closed JBMESSAGING-1249.
----------------------------------------
Resolution: Done
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Andy Taylor
Fix For: 1.4.1.CR1
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in
cluster and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:07 p.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=all ]
Clebert Suconic reopened JBMESSAGING-1249:
------------------------------------------
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Andy Taylor
Fix For: 1.4.1.CR1
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in
cluster and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:07 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=all ]
Clebert Suconic updated JBMESSAGING-1249:
-----------------------------------------
Fix Version/s: 1.4.0.SP3.CP02
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Andy Taylor
Fix For: 1.4.0.SP3.CP02, 1.4.1.CR1
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in
cluster and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:09 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=all ]
Clebert Suconic closed JBMESSAGING-1249.
----------------------------------------
Resolution: Done
Faiilover does not occur if last node in cluster is not available
-----------------------------------------------------------------
Key: JBMESSAGING-1249
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Andy Taylor
Fix For: 1.4.1.CR1, 1.4.0.SP3.CP02
A user has reported this and we need to verify if this is a real issue.
Use a connection factory with supportsFailover = true.
Two nodes in cluster.
Failover from one to another. Kill last one. Client should detect no more nodes in
cluster and throw exception back to user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6117
days inactive
6150
days old
12 comments
4 participants
participants (4)
-
Andy Taylor (JIRA) -
bodri bodri (JIRA)
-
Clebert Suconic (JIRA)
-
Tim Fox (JIRA)