Closing consumer does not free server memory, server heap overflows
-------------------------------------------------------------------

                 Key: AMQ-1062
                 URL: https://issues.apache.org/activemq/browse/AMQ-1062
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 4.2.0
         Environment: Windows XP Professional, Java HotSpot(TM) Client VM 
version 1.5.0_09-b01
            Reporter: [EMAIL PROTECTED]
            Priority: Critical
             Fix For: 4.2.0


I am using the store durable pending cursor.

Create a producer for a topic and let it run continuously for the remainder of 
the test.
Create a durable consumer and kill it immediately.  (So now messages are piling 
up for the consumer, but memory usage is low thanks to the store cursor.)
Wait a few minutes.
Now, start the same durable consumer again.
Memory usage will increase considerably at this point (I get it around 20%).
Now, stop the consumer.
Memory usage DOES NOT go down.
Now, reconnect the same durable consumer.  It is possible to get a heap overrun 
that nukes the server!

This is a problem when there are many consumers, and  the general use case is 
that many of them are not active at the same time.  I am classifying this as 
"critical bug" due to the heap overflow whenI try to reconnect, but it would be 
great if the memory usage went down as soon as disconnect.

I image there may also be problems like this with queues, but did not test.

2006-11-19 17:24:20,015 [/127.0.0.1:3278] DEBUG PrefetchSubscription           
- Prefetch limit.
2006-11-19 17:24:21,281 [/127.0.0.1:3278] DEBUG Service                        
- Error occured while processing sync command: java.lang.OutOfMemoryError: Java 
heap space
java.lang.OutOfMemoryError: Java heap space


-- 
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 via email to