Destroying durable subscription, does not entirely destory the durable subsciber
--------------------------------------------------------------------------------
Key: AMQ-1135
URL: https://issues.apache.org/activemq/browse/AMQ-1135
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.1.0
Environment: Linux 2.6.9-34.EL i686 i686 i386, Intel(R) Pentium(R) 4
CPU 2.80GHz, 2GB memory
Reporter: Sandeep Chayapathi
Attachments: jconsole.gif
Destroying a durable subcriber, via jconsole or by programmatically, does not
remove the durable subscriber. Over a period of time, once the memory reaches
the memorymanager limit, is causing "out of memory" exception.
Steps to duplicate:
1. start activemq, with a memorymanager limit of 10 MB
2. start a consumer, as a durable subscriber (you can use the bundled example
ConsumerTool.java), for a topic.
3. start a producer to send messages to the topic
4. kill the consumer, followed by the producer
5. use jconsole to connect to the activemq server
6. select the brokers "Operations" tab
7. delete the durable subscriber - notice the earlier subscription is never
removed, instead moved to a "false" subscription state
8. start the producer again - notice the memory usage increases, upto the 10MB
limit, and a "out of memory" exception is thrown
Attached is a screenshot of my jconsole showing the "false" subscription state.
This never occurred in AMQ 4.0.2 or 4.0.1, hence this must be a regression bug.
I would appreciate either a fix/patch or a workaround solution for this issue,
as this is one of the issues holding us from moving AMQ to a production setup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
