[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1249) Faiilover does not occur if last node in cluster is not available
bodri bodri (JIRA)
jira-events at lists.jboss.org
Fri Mar 14 04:42:57 EDT 2008
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1249?page=comments#action_12402853 ]
bodri bodri commented on JBMESSAGING-1249:
------------------------------------------
Note that the consumer is design, so that it survives cluster restarts (it uses the ExceptionListener).
The actual scenrio is:
1. Starting cluster node0
2. Starting standalone consumer (connected to node0)
3. Starting standalone producer - consumer receives the messages (OK)
4. Starting cluster node1
5. kill cluster node0 (consumer failover transparently on node1)
6. Starting standalone producer - consumer receives the messages (OK)
7. kill cluster node1 - no cluster and no exception callback on the consumer, so it thinks it is connected (not OK)
> 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: Tim Fox
> Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
>
>
> 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