[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address

[Jay Howell (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-947?page=comments#action_12360610 ] 
            
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