[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1027) Client updating fails

[Tim Fox (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1027?page=comments#action_12371982 ] 
            
Tim Fox commented on JBMESSAGING-1027:
--------------------------------------

There are two distinct major issues with the current client side failover info updating code:

1)
I download a connection factory
The network topology changes
I create a connection
The network topology is never updated on the client side

2)
I download a connection factory
The network topology changes such that none of the original nodes exist any more
I attempt to create a connection - this fails since none of the original nodes exist any more

The fundamental issue in the current implementation is that the updates are done on the *connection* - they should be done on the connection factory.

We need updates to happen even if there are no connections!!

> Client updating fails
> ---------------------
>
>                 Key: JBMESSAGING-1027
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1027
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.CR2
>
>
> Client side node list updating currently only occurs if there is an active connection on the connection factory.
> This means that if a connection factory is downloaded, then a node dies, or another joins, then a connectionm is created. The client side aspects will never know about the new topology.

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