Failover reconnect doesn't work correct in NMS 1.5.0 and memory usage is still 
growing.
---------------------------------------------------------------------------------------

                 Key: AMQNET-305
                 URL: https://issues.apache.org/jira/browse/AMQNET-305
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: ActiveMQ, NMS
    Affects Versions: 1.5.0
         Environment: windows 7
            Reporter: Kaminiecki
            Assignee: Jim Gomes
            Priority: Critical


I use  four brokers 5.4.2 in the cluster.
activemq client 1.4.1 and new NMS 1.5.0


I just started testing a new NSM 1.5.0 and I had a problem with the network 
through which I have not had access to three of the brokers during the test.
However, I had one visible on the network but the client did not switched to. 
Just so happens that one is in a different subnet than the three others.
I had three clients connected to one topic with the uri  failover (4 brokes 
url) All clients had the same uri. One of them was sending 10 messages per 
second.
When network connection dissapeard with three of the brokers. Message producer 
began to consume more memory. It was growing and growing. 
When I wanted to stop them, the producer stuck!


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to