activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (AMQ-3567) The InactivityMonitor onException call interrupts itself when the readCheckTime was exceeded.
Date Wed, 26 Oct 2011 18:37:32 GMT


Timothy Bish resolved AMQ-3567.

       Resolution: Fixed
    Fix Version/s:     (was: 5.5.1)
                       (was: 5.5.0)

Applied the patch, made some mods to the test to remove the hardcoding of port 61616.

> The InactivityMonitor onException call interrupts itself when the readCheckTime was exceeded.
> ---------------------------------------------------------------------------------------------
>                 Key: AMQ-3567
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.5.0, 5.5.1
>            Reporter: Claudio Corsi
>            Priority: Trivial
>              Labels: patch
>             Fix For: 5.6.0
>         Attachments: inactivitymonitor.patch
> The process that activemq uses to check if there has been inactivity for a connection
has a flaw when it tries to close the connection because of inactivity. The current process
generates the following interrupt exception. 
> {code} 
> 2011-10-25 12:13:56,878 | DEBUG | org.apache.activemq.util.ServiceSupport - Could not
stop service: tcp://localhost/ Reason: java.lang.InterruptedException
> java.lang.InterruptedException
>     at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(
>     at java.util.concurrent.CountDownLatch.await(
>     at org.apache.activemq.transport.tcp.TcpTransport.doStop(
>     at org.apache.activemq.util.ServiceSupport.stop(
>     at org.apache.activemq.transport.tcp.TcpTransport.stop(
>     at org.apache.activemq.transport.InactivityMonitor.stop(
>     at org.apache.activemq.transport.TransportFilter.stop(
>     at org.apache.activemq.transport.WireFormatNegotiator.stop(
>     at org.apache.activemq.util.ServiceSupport.dispose(
>     at org.apache.activemq.transport.failover.FailoverTransport.disposeTransport(
>     at org.apache.activemq.transport.failover.FailoverTransport.handleTransportFailure(
>     at org.apache.activemq.transport.failover.FailoverTransport$3.onException(
>     at org.apache.activemq.transport.TransportFilter.onException(
>     at org.apache.activemq.transport.WireFormatNegotiator.onException(
>     at org.apache.activemq.transport.InactivityMonitor.onException(
>     at org.apache.activemq.transport.InactivityMonitor$
>     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>     at java.util.concurrent.ThreadPoolExecutor$
>     at
> {code} 
> This is caused because the spawned thread in the AbstractInactivityMonitor classes readCheck
method calls the onException method. This method will then call the stopMonitorThreads method
which subsequently calls the shutdownNow method of the ASYNC_TASKS executor. This call causes
the executor to call the interrupt method for all active threads in the executor. The problem
is that the calling thread is part of the ASYNC_TASKS executor and therefore it is generating
the interrupt exception. 
> Here is the stack trace of the call that is causing the interrupt. 
> {code} 
> Daemon Thread [InactivityMonitor Async Task: java.util.concurrent.ThreadPoolExecutor$Worker@66da9ea4]
(Suspended (entry into method interrupt in Thread))   
>     Thread.interrupt() line: 902   
>     ThreadPoolExecutor$Worker.interruptNow() line: 855   
>     ThreadPoolExecutor.shutdownNow() line: 1167   
>     InactivityMonitor.stopMonitorThreads() line: 363   
>     InactivityMonitor.onException(IOException) line: 264   
>     InactivityMonitor$ line: 185   
>     ThreadPoolExecutor$Worker.runTask(Runnable) line: 886   
>     ThreadPoolExecutor$ line: 908   
> line: 680  
> {code} 
> The solution is to replace the shutdownNow method call with shutdown. Subsequent testing
with this change does not cause the interrupt exception. 
> I was able to create a testcase that reproduces this issue. The testcase uses the useInactivityMonitor=false
attribute to reproduce this issue, thanks Gary for the hint. Unfortunately there aren't any
steps that I can use to determine that the raised interrupted exception was raised or not.
The test will pass either way. 
> A patch will be added to this issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message