activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3393) Number of established STOMP connections constantly increasing
Date Tue, 05 Jul 2011 15:26:16 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully resolved AMQ-3393.
-----------------------------

    Resolution: Fixed

issue resolved in http://svn.apache.org/viewvc?rev=1143080&view=rev

stomp disconnect was bypassing delayed shutdown so in the event that a disconnect occurs before
a connect is fully formed, the connection was only partially disposed resulting in dangling
mbean references.

> Number of established STOMP connections constantly increasing
> -------------------------------------------------------------
>
>                 Key: AMQ-3393
>                 URL: https://issues.apache.org/jira/browse/AMQ-3393
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.5.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: jmx, memory, memory_leak, stomp
>             Fix For: 5.6.0
>
>
> Rapid connect/disconnect can result in dangling stomp transport connection mbeans which
eventually accumulate.
> Issue occurs when a disconnect occurs before a broker connection has been fully initiated.
The delayed stop, pending start completion was bypassed by a shutdown command from the stomp
protocol convertor.
> One potential symptom, when a client side port wrapps around and is reused for the MBean
name. There is a registration failure, with {code}2011-06-15 12:27:22,860 [eMQ Task-125034]
WARN  ManagedTransportConnection     - Failed to register MBean: org.apache.activemq:BrokerName=xx,Type=Connection,ConnectorName=stomp,ViewType=address,Name=/xx_52170
> 2011-06-15 12:27:22,860 [eMQ Task-125034] DEBUG ManagedTransportConnection     - Failure
reason: javax.management.InstanceAlreadyExistsException: org.apache.activemq:BrokerName=xx,Type=Connection,ConnectorName=stomp,ViewType=address,Name=/xx_52170
> javax.management.InstanceAlreadyExistsException: org.apache.activemq:BrokerName=xx,Type=Connection,ConnectorName=stomp,ViewType=address,Name=/xx_52170
> 	at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
> 	at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
> 	at org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:299)
> 	at org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:65)
> 	at org.apache.activemq.broker.jmx.ManagedTransportConnection.registerMBean(ManagedTransportConnection.java:99)
> 	at org.apache.activemq.broker.jmx.ManagedTransportConnection.<init>(ManagedTransportConnection.java:57)
> 	at org.apache.activemq.broker.jmx.ManagedTransportConnector.createConnection(ManagedTransportConnector.java:52)
> 	at org.apache.activemq.broker.TransportConnector$1$1.run(TransportConnector.java:216)
> 	at java.lang.Thread.run(Thread){code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message