[JBoss JIRA] Created: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
9:01 a.m.
Clustered messaging throws exceptions when failover happens in the clustered postoffice -
cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Tim Fox
The scenario is:
- 172.26.101.67 starts messaging
- 172.26.101.71 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.71 is stopped. This causes the stack trace on 172.26.101.67
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
9:03 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=all ]
Jay Howell updated JBMESSAGING-947:
-----------------------------------
Component/s: Messaging Core
Affects Version/s: 1.2.0.SP1
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Tim Fox
The scenario is:
- 172.26.101.67 starts messaging
- 172.26.101.71 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.71 is stopped. This causes the stack trace on 172.26.101.67
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
9:05 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=all ]
Jay Howell updated JBMESSAGING-947:
-----------------------------------
Attachment: server.log
This is the server.log with trace enabled for the clusterd post office package. This
should shed a little light on the subject.
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Tim Fox
Attachments: server.log
The scenario is:
- 172.26.101.67 starts messaging
- 172.26.101.71 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.71 is stopped. This causes the stack trace on 172.26.101.67
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
9:07 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=all ]
Jay Howell updated JBMESSAGING-947:
-----------------------------------
Description:
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.71 is stopped. This causes the stack trace on 172.26.101.67
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
was:
The scenario is:
- 172.26.101.67 starts messaging
- 172.26.101.71 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.71 is stopped. This causes the stack trace on 172.26.101.67
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Tim Fox
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.71 is stopped. This causes the stack trace on 172.26.101.67
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
9:07 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=all ]
Jay Howell updated JBMESSAGING-947:
-----------------------------------
Description:
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
was:
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.71 is stopped. This causes the stack trace on 172.26.101.67
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Tim Fox
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
9:26 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=all ]
Tim Fox updated JBMESSAGING-947:
--------------------------------
Fix Version/s: 1.2.0.SP2
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Tim Fox
Fix For: 1.2.0.SP2
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
9:26 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-947:
-------------------------------------
Can this be replicated
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Tim Fox
Fix For: 1.2.0.SP2
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
9:40 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=all ]
Tim Fox updated JBMESSAGING-947:
--------------------------------
Comment: was deleted
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Tim Fox
Fix For: 1.2.0.SP2
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
9:40 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-947:
-------------------------------------
Can this be replicated?
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Tim Fox
Fix For: 1.2.0.SP2
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
1:18 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=comments#action_12... ]
Jay Howell commented on JBMESSAGING-947:
----------------------------------------
Hey I was able to reproduce this. This error happens when you specify two nodes with the
same id and then fail-over happens on the first box. Set up two instances in a cluster.
change the node id in both to 0. You can do this on the same machine using the Messaging
install for different ports.
<mbean code="org.jboss.jms.server.ServerPeer"
name="jboss.messaging:service=ServerPeer"
xmbean-dd="xmdesc/ServerPeer-xmbean.xml">
<constructor>
<!-- ServerPeerID -->
<arg type="int" value="0"/>
Steps to reproduce .
Bring 1st node up
Bring 2nd node up
Down 1st node
2nd node shows the exception..
14:06:16,468 INFO [DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered
JMS:10.17.1.132:33003] got new view [10.17.1.132:32990|2] [10.17.1.132:33003]
14:06:16,469 ERROR [DefaultClusteredPostOffice] Caught Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:10.17.1.132:33003]
cannot find node ID for address 10.17.1.132:32990
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
14:06:16,470 ERROR [STDERR] Exception in thread "Thread-7"
14:06:16,470 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:10.17.1.132:33003] cannot find node ID for address
10.17.1.132:32990
14:06:16,470 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
14:06:16,471 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
14:06:16,471 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
14:06:16,471 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
14:06:16,471 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
What should happen is that if you attempt to join a cluster with a node id that is already
taken, it should throw an exception and fail to start.
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Tim Fox
Fix For: 1.2.0.SP2
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
1:22 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=all ]
Clebert Suconic updated JBMESSAGING-947:
----------------------------------------
Fix Version/s: (was: 1.2.0.SP2)
Assignee: Clebert Suconic (was: Tim Fox)
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Clebert Suconic
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
1:22 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=all ]
Clebert Suconic closed JBMESSAGING-947.
---------------------------------------
Resolution: Won't Fix
I have opened JBMESSAGING-948 that would avoid this message.
For this issue all you have to do is to have dintinct IDs on ServerPeer.
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Clebert Suconic
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
1:52 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=comments#action_12... ]
Jay Howell commented on JBMESSAGING-947:
----------------------------------------
Sure, that is true, but the number of customers that will not configure this properly will
probably high. I understand that we can hide th e error during failover, but what is the
impact if we have duplicate node ids. I would assume that this is fairly important and
having duplicate ids could be bad. Shouldn't we throw exceptions when bringing up
nodes telling the users that they have a duplicate node id. So I guess I disagree that we
should hide the error. unless the node id doesn't really matter.
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Clebert Suconic
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
1:54 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-947:
---------------------------------------------
Shouldn't we throw exceptions when bringing up nodes telling the
users that they have a duplicate node id
That's why I opened JBMESSAGING-948.
I'm not ignoring the issue.
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Clebert Suconic
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
1:56 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=comments#action_12... ]
Jay Howell commented on JBMESSAGING-947:
----------------------------------------
sorry about that, I put this in before I read the other defect. Jay:)
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Clebert Suconic
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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:51 a.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=all ]
Tim Fox reopened JBMESSAGING-947:
---------------------------------
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Clebert Suconic
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
9:57 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address
[ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=all ]
Clebert Suconic closed JBMESSAGING-947.
---------------------------------------
Resolution: Won't Fix
Clustered messaging throws exceptions when failover happens in the
clustered postoffice - cannot find node ID for address
-------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-947
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.2.0.SP1
Environment: Clusterd Messaging using Remoting 2.2.0 SP1
Reporter: Jay Howell
Assigned To: Clebert Suconic
Attachments: server.log
The scenario is:
- 172.26.101.71 starts messaging
- 172.26.101.67 starts messaging and joins the cluster. The postoffices are now in a
clustered state
- Messaging on 172.26.101.67 is stopped. This causes the stack trace on 172.26.101.71
2007-04-19 15:58:46,675 DEBUG
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice]
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left
2007-04-19 15:58:46,675 ERROR
[org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught
Exception in MembershipListener
java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]
cannot find node ID for address 172.26.101.67:52432
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28"
2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException:
ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address
172.26.101.67:52432
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98)
2007-04-19 15:58:46,675 ERROR [STDERR] at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400)
2007-04-19 15:58:46,675 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted():
[lonrs00341:54163|2] [lonrs00341:54163]
2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null:
members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5
--
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
6920
days inactive
6926
days old
16 comments
3 participants
participants (3)
-
Clebert Suconic (JIRA) -
Jay Howell (JIRA)
-
Tim Fox (JIRA)