activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Abramov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1135) Destroying durable subscription, does not entirely destory the durable subsciber
Date Mon, 29 Oct 2007 14:50:23 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40527
] 

Denis Abramov commented on AMQ-1135:
------------------------------------

Also same problem. It was OK in AMQ 4.0.1 & 4.0.2 but started happening when we switched
to 4.1.1. I am now getting:

javax.jms.InvalidClientIDException: Broker: localhost - Client: com.pgam.messaging.services.EQSecurityDescService
already connected
	at org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:204)
	at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:82)
	at org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:70)
	at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:82)
	at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:92)
	at org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:706)
	at org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:86)
	at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:121)
	at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:294)
	at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:185)
	at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
	at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133)
	at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
	at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)

> 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
>             Fix For: 5.2.0
>
>         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.


Mime
View raw message