]
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: