[jira] Updated: (AMQ-847) Memory Leaks
[ https://issues.apache.org/activemq/browse/AMQ-847?page=all ] james strachan updated AMQ-847: --- Fix Version/s: 4.0.3 (was: 4.0.2) Memory Leaks Key: AMQ-847 URL: https://issues.apache.org/activemq/browse/AMQ-847 Project: ActiveMQ Issue Type: Bug Components: Broker Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.0.3 1) factoryStats in the connection factory was holding on to connections even when they are closed. 2) peer BrokerInfos were never removed even when the peer disconnected. 3) messages dispatched from a Queue would retain a referece to the client connection even after they had been acked. 4) ScheduledThreadPoolExecutor does not always seem to release references to canceled tasks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-847) Memory Leaks
[ https://issues.apache.org/activemq/browse/AMQ-847?page=all ] Hiram Chirino updated AMQ-847: -- Fix Version/s: 4.0.2 (was: 4.1) (was: 4.0.3) Memory Leaks Key: AMQ-847 URL: https://issues.apache.org/activemq/browse/AMQ-847 Project: ActiveMQ Issue Type: Bug Components: Broker Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.0.2 1) factoryStats in the connection factory was holding on to connections even when they are closed. 2) peer BrokerInfos were never removed even when the peer disconnected. 3) messages dispatched from a Queue would retain a referece to the client connection even after they had been acked. 4) ScheduledThreadPoolExecutor does not always seem to release references to canceled tasks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
