[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available

Andy Taylor (JIRA) jira-events at lists.jboss.org
Tue Mar 25 13:19:42 EDT 2008


     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=all ]

Andy Taylor closed JBMESSAGING-1249.
------------------------------------

    Fix Version/s: Stable branch
                       (was: 1.4.1.beta2)
       Resolution: Done

The problem was that when fail over occurred and the client reconnected the exception listener was not being set on the newly created connection. This is now fixed

> Faiilover does not occur if last node in cluster is not available
> -----------------------------------------------------------------
>
>                 Key: JBMESSAGING-1249
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1249
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Andy Taylor
>             Fix For: 1.4.0.SP3.CP02, Stable branch
>
>
> A user has reported this and we need to verify if this is a real issue.
> Use a connection factory with supportsFailover = true.
> Two nodes in cluster.
> Failover from one to another. Kill last one. Client should detect no more nodes in cluster and throw exception back to user.

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

        



More information about the jboss-jira mailing list