activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "klas eriksson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-847) Memory Leaks
Date Fri, 15 Dec 2006 07:43:02 GMT
    [ https://issues.apache.org/activemq/browse/AMQ-847?page=comments#action_37686 ] 
            
klas eriksson commented on AMQ-847:
-----------------------------------

I think this issue is actually *two* (or more:) memory leaks.
One in createConnection() and one in close().
I tried a very similar program with the following results:

apache-activemq-4.2-incubator-20061204.023752-14:
1. 'createConnection' followed by 'close' when activeMq-server is UP:
   outOfmemory after ~1800 createConnection-close.

2. 'createConnection' without close when activeMq server is not started.
  outOfmemory after < 1800 failed 'createConnection'.

I have also tried 4.0.x and 4.1.x. The leak memory too.

> 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

        

Mime
View raw message