activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-305) Failover reconnect doesn't work correct in NMS 1.5.0 and memory usage is still growing.
Date Wed, 26 Jan 2011 21:40:44 GMT

    [ https://issues.apache.org/jira/browse/AMQNET-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987238#action_12987238
] 

Timothy Bish commented on AMQNET-305:
-------------------------------------

I think this may be resolved in the trunk as far as memory consumption goes.   I don't have
the resources to test the multiple subnet scenario.

> 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!
> Now I found somthing interesting more the 4th broker was stopped so so in this case no
working broker or destination with brokers were available.

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


Mime
View raw message