[ https://issues.apache.org/activemq/browse/AMQ-847?page=all ]
Helmut Janknecht reopened AMQ-847:
----------------------------------
There seems to be still some more leaks, try the following junit test with
4.0.2 RC4:
{code}
public void testCreateConnectionMemoryLeak() throws Exception {
Connection c = null;
// ACXMessagingFactory messagingFactory =
this.getSessionContext().getFactoryContext().getMessagingFactory();
ActiveMQConnectionFactory messagingFactory = new
ActiveMQConnectionFactory("tcp://localhost:61616");
boolean closed = false;
for (int i = 0; i < 10000; i++) {
try {
c = messagingFactory.createConnection();
closed = false;
c.close();
closed = true;
} finally {
if (!closed) {
c.close();
}
}
}
}
{code}
> 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
