[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-724) Client managed failover: messages sent to healthy server end up trying to connect to failed node

[Galder Zamarreno (JIRA)]

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

Galder Zamarreno updated JBMESSAGING-724:
-----------------------------------------

    Attachment: TestMultiConnectionMessageProducer.java

test case

> Client managed failover: messages sent to healthy server end up trying to connect to failed node
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-724
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-724
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Remoting
>    Affects Versions: 1.0.1.GA, 1.2.0.Beta1
>            Reporter: Galder Zamarreno
>         Assigned To: Ovidiu Feodorov
>         Attachments: replicated-1.0.1.GA-jbossmessaging.log, TestMultiConnectionMessageProducer.java
>
>
> The attached test case creates connections to two standalone messaging AS
> servers. It initially sends messages to the first of servers until it fails. At this point, 
> it switches to the second one.
> This works fine, but at some point in the failover, when the client is sending the 
> messages to the second node, it fails because it attempts to send something again 
> to the first server. This fails with java.net.ConnectException: Connection refused: connect
> because the first server is already down (replicated-1.0.1.GA-jbossmessaging.log: L12869 ).
> At line 1208, we shut down server 1 and we start trying to send messages to server 2. After 
> sending a few messages successfully to server 2, suddenly, there's an attempt to connect 
> back to server 1 which fails.
> I have attached a client log with TRACE on org.jboss and TestMultiConnectionMessageProducer.java 
> which is the test case.
> I was able to replicate this is in 1.0.1.GA and 1.2.0.Beta1 but not 1.2.0.Alpha2.
> Forum link fix focuses on the message comsumption area (CallbackManager), but does not
> provide further information on what might have changed in 1.2.0.Alpha2 to indicate that this is trully solved.

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