[jira] Updated: (AMQNET-305) Failover reconnect doesn't work correct in NMS 1.5.0 and memory usage is still growing.

[ https://issues.apache.org/jira/browse/AMQNET-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-305: Fix Version/s: (was: 1.5.0) Since this is really a broker related issue I'm removing the NMS

[jira] Updated: (AMQNET-305) Failover reconnect doesn't work correct in NMS 1.5.0 and memory usage is still growing.

[ https://issues.apache.org/jira/browse/AMQNET-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-305: - Component/s: (was: NMS) Failover reconnect doesn't work correct in NMS 1.5.0 and memory usage is

[jira] Updated: (AMQNET-305) Failover reconnect doesn't work correct in NMS 1.5.0 and memory usage is still growing.

[ https://issues.apache.org/jira/browse/AMQNET-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-305: - Fix Version/s: 1.5.0 Failover reconnect doesn't work correct in NMS 1.5.0 and memory usage is still

[jira] Updated: (AMQNET-305) Failover reconnect doesn't work correct in NMS 1.5.0 and memory usage is still growing.

[ https://issues.apache.org/jira/browse/AMQNET-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaminiecki updated AMQNET-305: -- Description: I use four brokers 5.4.2 in the cluster. activemq client 1.4.1 and new NMS 1.5.0 I