[
https://issues.apache.org/jira/browse/AMQ-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-3286.
-----------------------------
Resolution: Cannot Reproduce
Tried a couple different tests but couldn't reproduce this issue, if you have a
test case that can demonstrate the issue please reopen and attach it.
> ActiveMQ Connection Dispatcher thread
> -------------------------------------
>
> Key: AMQ-3286
> URL: https://issues.apache.org/jira/browse/AMQ-3286
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.0, 5.3.2
> Environment: == Java ==
> java version "1.6.0_20"
> Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
> == ActiveMQ ==
> - Versions: 5.3.0 and 5.3.2
> - Pure Master/Slave
> - Openwire enabled
> - FlowControl enabled
> - KahaDB
> Reporter: Simon-Pierre LeBel
>
> I'm having some issues with ActiveMQ Connection Dispatcher threads. Whenever
> I get an InactivityIOException the thread goes into the Waiting state and a
> new thread is started.
> == activemq.log ==
> 2011-04-18 10:15:31,244 | ERROR | Could not accept connection :
> org.apache.activemq.transport.InactivityIOException: Channel was inactive for
> too long: /127.0.0.1:35401 | org.apache.activemq.broker.TransportConnector |
> ActiveMQ Task
> == jstack ==
> "ActiveMQ Connection Dispatcher: /127.0.0.1:35401" daemon prio=10
> tid=0x00007f10e440f800 nid=0x63e9 in Object.wait() [0x00007f10ce578000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:485)
> at
> org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:105)
> - locked <0x00007f113bbd4618> (a java.lang.Object)
> at
> org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:36)
> After running ActiveMQ for a couple of weeks there are more than 3k waiting
> threads doing nothing but wasting memory. If i disable the inactivity monitor
> the problem goes away (wireFormat.maxInactivityDuration=0).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
