[jira] Created: (AMQ-847) Memory Leaks

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (AMQ-847) Memory Leaks

JIRA jira@apache.org
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, 4.1


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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (AMQ-847) Memory Leaks

JIRA jira@apache.org
    [ https://issues.apache.org/activemq/browse/AMQ-847?page=comments#action_36646 ]
           
Hiram Chirino commented on AMQ-847:
-----------------------------------

Fixed in 4.0 branch rev 425922

> 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, 4.1
>
>
> 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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (AMQ-847) Memory Leaks

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org
    [ https://issues.apache.org/activemq/browse/AMQ-847?page=comments#action_36647 ]
           
james strachan commented on AMQ-847:
------------------------------------

I think  1) is a duplicate of AMQ-835 maybe?

> 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, 4.1
>
>
> 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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (AMQ-847) Memory Leaks

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org
     [ https://issues.apache.org/activemq/browse/AMQ-847?page=all ]

Hiram Chirino resolved AMQ-847.
-------------------------------

    Resolution: Fixed

> 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, 4.1
>
>
> 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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (AMQ-847) Memory Leaks

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org
    [ https://issues.apache.org/activemq/browse/AMQ-847?page=comments#action_36651 ]
           
Hiram Chirino commented on AMQ-847:
-----------------------------------

your right.  the rest of the issue fixed in 4.1 branch rev 426134.

> 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.1, 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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (AMQ-847) Memory Leaks

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org
     [ 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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Reopened: (AMQ-847) Memory Leaks

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org
     [ 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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (AMQ-847) Memory Leaks

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org
     [ 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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (AMQ-847) Memory Leaks

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org
    [ 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