[
https://issues.apache.org/activemq/browse/AMQ-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42035#action_42035
]
Rob Davies commented on AMQ-1626:
---------------------------------
Does this happen with Spring 2.5 ?
> Active MQ version 5.X - java 5 - memory leaks
> ----------------------------------------------
>
> Key: AMQ-1626
> URL: https://issues.apache.org/activemq/browse/AMQ-1626
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.0.0, 5.1.0
> Reporter: Michal Singer
> Priority: Blocker
> Attachments: ClientExecuterController.java, JmsListener.java,
> JmsResponseSender.java
>
>
> when working with jdk1.5 and activemq 5.X. there are problems with memory
> leaks.
> I use an embedded broker configured in spring 2.0.8.
> I have a client application (producer ) and a server (consumer) which inside
> it the broker.
> The client uses PooledConnectionFactory, creates one connection, 2 sessions
> (receive and send), and 1 producer.
> the client connects to 2 queues defined in the broker (configured in spring),
> and sets the "reply to" to a temporary queue.
> The server receives the messages from the client, does some processing, and
> returns a reply on the temp q.
> each request is handled by a diiferent temp q. the temp q is deleted once the
> client receives the responses.
> All resources are deleted on client side. the server is hanlded by spring.
> the server responses on the temp queues.
> During run, i see a few problems (in jconsole)
> 1. memory of broker increases gradually and never released
> 2. memory of temp queues increases gradually and never released
> 3. advisory topic node is created with many objects under it - which seem
> like with the same ids as some of the temp queue. they accumulate,
> and are never released.
> These leaks prevent me from working,. the activemq will stop working after a
> few hours due to 100%memory consumption.
> There are also memory leaks concerning temp queues usage.
> I tried creating one connection on client or using a pool of connections but
> nothing helped.
> It looks like some memory leak on the temp queues.
> Do you have a work around for these problems, when will there be fixes for
> these problems?
> If i will use a static queues, will all the leaks in the broker be solved?
> If i create a new connection for each request process, should this solve the
> problem? (checked - does not work)
> I attached the client (producer) code and the server (consumer)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
