activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mario Siegenthaler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1437) Memory Leak in Resource Adapator?
Date Mon, 06 Jul 2009 15:28:07 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52709#action_52709
] 

Mario Siegenthaler commented on AMQ-1437:
-----------------------------------------

Duplicate of AMQ-2166 (contains a fix)

Actually mine was the duplicate of this (didn't find it then, I appologize)

> 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
>             Fix For: 5.4.0
>
>         Attachments: mem-histo.2008.10.03.txt
>
>
> 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.


Mime
View raw message