[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] Created: (AMQ-1437) Memory Leak in Resource Adapator?
From:       "Steven Buberl (JIRA)" <jira () apache ! org>
Date:       2007-09-28 16:16:23
Message-ID: 6971114.1190996183005.JavaMail.jira () brutus
[Download RAW message or body]

Memory Leak in Resource Adapator?
---------------------------------

                 Key: AMQ-1437
                 URL: https://issues.apache.org/activemq/browse/AMQ-1437
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMS client
         Environment: Ran on ActiveMQ 4.1.1 but ActiveMQ 5.0's code is the same

            Reporter: Steven Buberl


I think it is a memory leak that calling close() on a \
org.apache.activemq.ra.ManagedSessionProxy does not remove it from the session list \
of the org.apache.activemq.ra.ManagedConnectionProxy that created it.  Some programs \
(like mine) run on a Jboss bean thats generating messages every few seconds and I \
like to keep a Connection open to ActiveMQ and create a new session for each new \
batch of messages.  When I close these sessions (which are really \
ManagedSessionProxy's), the actual ActiveMQSession wrapped inside closes but a lot of \
its data remains referenced inside it.   Also, the reference to the \
ManagedSessionProxy stays in the ManagedConnectionProxy's session list.  So since the \
ManagedSessionProxy has to stay in the ManagedConnectionproxy's session list, it \
stays in memory and so does the ActiveMQSession, and so all these sessions (thousands \
of them) stay in memory until the ManagedConnectionProxy is closed which my program \
only calls when the server shuts down.

To generate this, create a simple message producing program that uses the resource \
adaptor's ActiveMQConnectionFactory to generate one connection.  Then run a loop that \
creates a session on that connection, sends a message or two, and closes the session. \
May need to run this loop at least 100 times appreciate what I'm saying and how \
quickly it affects things.

I think this will be a simple fix and hopefully will be resolved soon.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[prev in list] [next in list] [prev in thread] [next in thread]