[
https://issues.apache.org/activemq/browse/AMQ-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Singer reopened AMQ-1044:
--------------------------------
I saw this problem happen in 5.0 as well as snapshots of 5.1.
I get this error:
WARNING: Failed to register MBean:
org.apache.activemq:BrokerName=embeddedbroker,Type=Topic,Destination=ActiveMQ.Advisory.Producer.Queue.ID_1586-
...
I do have memory leaks as well as ActiveMQ.Advisory.Producer.Queue accumulation.
here are the objects which are leaking:
org.apache.activemq.filter.DestinationMapNode
org.apache.activemq.filter.SimpleDestinationFilter
org.apache.activemq.broker.region.policy.SimpleDispatchPolicy
org.apache.activemq.broker.region.policy.SharedDeadLetterStrategy
org.apache.activemq.broker.region.policy.NoSubscriptionRecoveryPolicy
org.apache.activemq.broker.region.Topic$1
org.apache.activemq.broker.region.Topic
org.apache.activemq.broker.region.DestinationStatistics
org.apache.activemq.broker.jmx.TopicView
org.apache.activemq.usage.MemoryUsage
org.apache.activemq.usage.DefaultUsageCapacity
org.apache.activemq.management.PollCountStatisticImpl
> Failed to register MBean error.
> -------------------------------
>
> Key: AMQ-1044
> URL: https://issues.apache.org/activemq/browse/AMQ-1044
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.0
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 4.1.1, 5.0.0
>
>
> If async error such as a inactivity IO exception is detected while a
> subscription is being created, then that subscription is not fully cleaned up
> when the connection is disposed. If the client is using failover and
> reconnects, then it gets a "Failed to register MBean error." Since the
> subscription is still registered in JMX. This is also a source of a memory
> leak since subscriptions are are left registered in JMX.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
