[JBoss JIRA] Created: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.
5:04 p.m.
Node failure does not trigger failover for new nodes entering the cluster.
--------------------------------------------------------------------------
Key: JBMESSAGING-1402
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402
Project: JBoss Messaging
Issue Type: Bug
Reporter: Jay Howell
Assignee: Tim Fox
When a node fails, users are reporting that the failure doesn't trigger a cluster
failover. When a member starts back up and tries to join, it experiences a failure trying
to reconnect to the downed node causing the container not to start.
Users are getting..
2008-07-18 08:42:53,211 144578 DEBUG
[org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of
the group so no need to wait for state
2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):)
-------------------------------------------------------
GMS: address is 69.52.50.155:7900
-------------------------------------------------------
2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
which occurs every 5 seconds and prevents the container from starting up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:04 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1402?page=com.atlassian.ji...
]
Jay Howell updated JBMESSAGING-1402:
------------------------------------
Component/s: JMS Clustering
Affects Version/s: 1.4.0.SP3.CP02
Node failure does not trigger failover for new nodes entering the
cluster.
--------------------------------------------------------------------------
Key: JBMESSAGING-1402
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Tim Fox
When a node fails, users are reporting that the failure doesn't trigger a cluster
failover. When a member starts back up and tries to join, it experiences a failure trying
to reconnect to the downed node causing the container not to start.
Users are getting..
2008-07-18 08:42:53,211 144578 DEBUG
[org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of
the group so no need to wait for state
2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):)
-------------------------------------------------------
GMS: address is 69.52.50.155:7900
-------------------------------------------------------
2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
which occurs every 5 seconds and prevents the container from starting up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:30 p.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1402?page=com.atlassian.ji...
]
Jay Howell reassigned JBMESSAGING-1402:
---------------------------------------
Assignee: Jay Howell (was: Tim Fox)
Node failure does not trigger failover for new nodes entering the
cluster.
--------------------------------------------------------------------------
Key: JBMESSAGING-1402
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Jay Howell
When a node fails, users are reporting that the failure doesn't trigger a cluster
failover. When a member starts back up and tries to join, it experiences a failure trying
to reconnect to the downed node causing the container not to start.
Users are getting..
2008-07-18 08:42:53,211 144578 DEBUG
[org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of
the group so no need to wait for state
2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):)
-------------------------------------------------------
GMS: address is 69.52.50.155:7900
-------------------------------------------------------
2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
which occurs every 5 seconds and prevents the container from starting up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:34 p.m.
New subject: [JBoss JIRA] Resolved: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1402?page=com.atlassian.ji...
]
Jay Howell resolved JBMESSAGING-1402.
-------------------------------------
Fix Version/s: 1.4.0.SP3.CP04
Resolution: Done
Node failure does not trigger failover for new nodes entering the
cluster.
--------------------------------------------------------------------------
Key: JBMESSAGING-1402
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Jay Howell
Fix For: 1.4.0.SP3.CP04
When a node fails, users are reporting that the failure doesn't trigger a cluster
failover. When a member starts back up and tries to join, it experiences a failure trying
to reconnect to the downed node causing the container not to start.
Users are getting..
2008-07-18 08:42:53,211 144578 DEBUG
[org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of
the group so no need to wait for state
2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):)
-------------------------------------------------------
GMS: address is 69.52.50.155:7900
-------------------------------------------------------
2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
which occurs every 5 seconds and prevents the container from starting up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:10 p.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1402?page=com.atlassian.ji...
]
Tim Fox reopened JBMESSAGING-1402:
----------------------------------
Node failure does not trigger failover for new nodes entering the
cluster.
--------------------------------------------------------------------------
Key: JBMESSAGING-1402
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Jay Howell
Fix For: 1.4.0.SP3.CP04
When a node fails, users are reporting that the failure doesn't trigger a cluster
failover. When a member starts back up and tries to join, it experiences a failure trying
to reconnect to the downed node causing the container not to start.
Users are getting..
2008-07-18 08:42:53,211 144578 DEBUG
[org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of
the group so no need to wait for state
2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):)
-------------------------------------------------------
GMS: address is 69.52.50.155:7900
-------------------------------------------------------
2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
which occurs every 5 seconds and prevents the container from starting up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:14 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1402?page=com.atlassian.ji...
]
Tim Fox updated JBMESSAGING-1402:
---------------------------------
Fix Version/s: 1.4.1.GA
Node failure does not trigger failover for new nodes entering the
cluster.
--------------------------------------------------------------------------
Key: JBMESSAGING-1402
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Jay Howell
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
When a node fails, users are reporting that the failure doesn't trigger a cluster
failover. When a member starts back up and tries to join, it experiences a failure trying
to reconnect to the downed node causing the container not to start.
Users are getting..
2008-07-18 08:42:53,211 144578 DEBUG
[org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of
the group so no need to wait for state
2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):)
-------------------------------------------------------
GMS: address is 69.52.50.155:7900
-------------------------------------------------------
2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
which occurs every 5 seconds and prevents the container from starting up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:12 p.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1402?page=com.atlassian.ji...
]
Clebert Suconic reassigned JBMESSAGING-1402:
--------------------------------------------
Assignee: Clebert Suconic (was: Jay Howell)
Node failure does not trigger failover for new nodes entering the
cluster.
--------------------------------------------------------------------------
Key: JBMESSAGING-1402
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Clebert Suconic
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
When a node fails, users are reporting that the failure doesn't trigger a cluster
failover. When a member starts back up and tries to join, it experiences a failure trying
to reconnect to the downed node causing the container not to start.
Users are getting..
2008-07-18 08:42:53,211 144578 DEBUG
[org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of
the group so no need to wait for state
2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):)
-------------------------------------------------------
GMS: address is 69.52.50.155:7900
-------------------------------------------------------
2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
which occurs every 5 seconds and prevents the container from starting up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:28 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1402?page=com.atlassian.ji...
]
Clebert Suconic commented on JBMESSAGING-1402:
----------------------------------------------
Jay used this WIKI:
http://wiki.jboss.org/auth/wiki/FDVersusFD_SOCK
Node failure does not trigger failover for new nodes entering the
cluster.
--------------------------------------------------------------------------
Key: JBMESSAGING-1402
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Clebert Suconic
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
When a node fails, users are reporting that the failure doesn't trigger a cluster
failover. When a member starts back up and tries to join, it experiences a failure trying
to reconnect to the downed node causing the container not to start.
Users are getting..
2008-07-18 08:42:53,211 144578 DEBUG
[org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of
the group so no need to wait for state
2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):)
-------------------------------------------------------
GMS: address is 69.52.50.155:7900
-------------------------------------------------------
2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
which occurs every 5 seconds and prevents the container from starting up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:54 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1402?page=com.atlassian.ji...
]
Clebert Suconic commented on JBMESSAGING-1402:
----------------------------------------------
To reproduce this issue, you would need a panic event to happen, such as power down,
network down.
Something that would keep the sockets alive.
All the other channels at AS & EAP are using both FD and FD_SOCK.
It would be nice to add a testcase for this, but this would require some manual steps to
reproduce this. To automate it we would need some sort of virtual machines where we would
be able to shut them down or some other things like that, but that goes beyond the scope
of this task.
Since this has been extensively tested by JGroups guys, I will just accept this as being
tested by JGropus.
Node failure does not trigger failover for new nodes entering the
cluster.
--------------------------------------------------------------------------
Key: JBMESSAGING-1402
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Clebert Suconic
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
When a node fails, users are reporting that the failure doesn't trigger a cluster
failover. When a member starts back up and tries to join, it experiences a failure trying
to reconnect to the downed node causing the container not to start.
Users are getting..
2008-07-18 08:42:53,211 144578 DEBUG
[org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of
the group so no need to wait for state
2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):)
-------------------------------------------------------
GMS: address is 69.52.50.155:7900
-------------------------------------------------------
2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
which occurs every 5 seconds and prevents the container from starting up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:56 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1402?page=com.atlassian.ji...
]
Clebert Suconic closed JBMESSAGING-1402.
----------------------------------------
Resolution: Done
Assignee: Jay Howell (was: Clebert Suconic)
Node failure does not trigger failover for new nodes entering the
cluster.
--------------------------------------------------------------------------
Key: JBMESSAGING-1402
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Jay Howell
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
When a node fails, users are reporting that the failure doesn't trigger a cluster
failover. When a member starts back up and tries to join, it experiences a failure trying
to reconnect to the downed node causing the container not to start.
Users are getting..
2008-07-18 08:42:53,211 144578 DEBUG
[org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of
the group so no need to wait for state
2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):)
-------------------------------------------------------
GMS: address is 69.52.50.155:7900
-------------------------------------------------------
2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
which occurs every 5 seconds and prevents the container from starting up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:17 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1402?page=com.atlassian.ji...
]
Clebert Suconic closed JBMESSAGING-1402.
----------------------------------------
Fix Version/s: 1.4.1.GA
Resolution: Done
Node failure does not trigger failover for new nodes entering the
cluster.
--------------------------------------------------------------------------
Key: JBMESSAGING-1402
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Jay Howell
Fix For: 1.4.1.GA, 1.4.2.GA, 1.4.0.SP3.CP04
When a node fails, users are reporting that the failure doesn't trigger a cluster
failover. When a member starts back up and tries to join, it experiences a failure trying
to reconnect to the downed node causing the container not to start.
Users are getting..
2008-07-18 08:42:53,211 144578 DEBUG
[org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of
the group so no need to wait for state
2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):)
-------------------------------------------------------
GMS: address is 69.52.50.155:7900
-------------------------------------------------------
2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
which occurs every 5 seconds and prevents the container from starting up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:17 a.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1402?page=com.atlassian.ji...
]
Clebert Suconic reopened JBMESSAGING-1402:
------------------------------------------
Node failure does not trigger failover for new nodes entering the
cluster.
--------------------------------------------------------------------------
Key: JBMESSAGING-1402
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Jay Howell
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA, 1.4.2.GA
When a node fails, users are reporting that the failure doesn't trigger a cluster
failover. When a member starts back up and tries to join, it experiences a failure trying
to reconnect to the downed node causing the container not to start.
Users are getting..
2008-07-18 08:42:53,211 144578 DEBUG
[org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of
the group so no need to wait for state
2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):)
-------------------------------------------------------
GMS: address is 69.52.50.155:7900
-------------------------------------------------------
2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:)
join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying
which occurs every 5 seconds and prevents the container from starting up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5710
days inactive
5819
days old
11 comments
3 participants
participants (3)
-
Clebert Suconic (JIRA) -
Jay Howell (JIRA)
-
Tim Fox (JIRA)