[ http://jira.jboss.com/jira/browse/JBAS-35?page=comments#action_12310859 ] Scott M Stark commented on JBAS-35: -----------------------------------
Can you verify that the issue does not exist in 4.0.0 or at least 4.0.1RC1? > InvalidDestinationException after Cluster Master failover > --------------------------------------------------------- > > Key: JBAS-35 > URL: http://jira.jboss.com/jira/browse/JBAS-35 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-3.2.5 Final > Reporter: Scott M Stark > Assignee: Ovidiu Feodorov > Fix For: JBossAS-3.2.6 Final > Attachments: JBossFailOverError.txt > > > See the attachment JBossFailOverError.txt for more details. > Abstract: I have a 2 node cluster running JbossMQHA. If the Master node is > disconnect from the Network, the slave assumes the master role. But when the > original Master comes back on-line, it reassumes the Master role, but my > subscriber is never notified of the 2nd fail-over and I am unable to publish > on the slave for about 5 minutes. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
