You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jamie goodyear (JIRA)" <ji...@apache.org> on 2018/09/16 12:00:00 UTC
[jira] [Commented] (AMQ-7033) Broker not cleaning up session during
high message rate
[ https://issues.apache.org/jira/browse/AMQ-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16616693#comment-16616693 ]
Jamie goodyear commented on AMQ-7033:
-------------------------------------
Please supply more information about the broker and client(s).
activemq.xml, any parameters passed in via env/start scripts.
Sample client(s).
What is the broker topology? Single broker, NOB, store & forward, etc.
> Broker not cleaning up session during high message rate
> -------------------------------------------------------
>
> Key: AMQ-7033
> URL: https://issues.apache.org/jira/browse/AMQ-7033
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.15.4
> Reporter: Yogeshkumar More
> Priority: Major
>
> When we try to send large number of messages from multiple connections we see that some of the sockets don't get cleaned up. We initially thought [AMQ-6561|https://issues.apache.org/jira/browse/AMQ-6561] AMQ-6561 should have fixed this. But even after upgrading the version to 5.15.4 we see socket leak. Following stack trace proves that there is some blocking which is not clearing up the sockets. This grows gradually and causes out of memory issue as we are using non-persistent, embedded broker.
>
> {code:java}
> "ActiveMQ InactivityMonitor Worker" #17953 daemon prio=5 os_prio=0 tid=0x00007fdc64017800 nid=0xb27f waiting for monitor entry [0x00007fda48fce000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at org.apache.activemq.broker.TransportConnection.stopAsync(TransportConnection.java:1136)
> - waiting to lock <0x00000006c2339d58> (a org.apache.activemq.broker.TransportConnection)
> at org.apache.activemq.broker.TransportConnection.stopAsync(TransportConnection.java:1131)
> at org.apache.activemq.broker.TransportConnection.serviceTransportException(TransportConnection.java:239)
> at org.apache.activemq.broker.TransportConnection$1.onException(TransportConnection.java:210)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
> at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173)
> at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:345)
> at org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:92)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)