activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vilius (JIRA)" <>
Subject [jira] [Created] (AMQ-4156) Inactivity monitor rejected from thread pool
Date Fri, 02 Nov 2012 18:07:13 GMT
vilius created AMQ-4156:

             Summary: Inactivity monitor rejected from thread pool
                 Key: AMQ-4156
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.5.1
         Environment: VM name: Java HotSpot(TM) 64-Bit Server VM
VM Version: 23.1-b03
VM Vendor: Oracle Corporation
            Reporter: vilius

2012/09/04 17:50:10.746 [UncaughtExceptionHandler] [InactivityMonitor WriteCheck]:   ERROR:
 FATAL ERROR Uncaught Exception occurred in thread Thread[InactivityMonitor WriteCheck,5,main]
[Exception: java.util.concurrent.RejectedExecutionException: Task org.apache.activemq.transport.InactivityMonitor$3@321e23e9
rejected from java.util.concurrent.ThreadPoolExecutor@58c7afb3[Terminated, pool size = 0,
active threads = 0, queued tasks = 0, completed tasks = 441]
	at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(
	at java.util.concurrent.ThreadPoolExecutor.reject(
	at java.util.concurrent.ThreadPoolExecutor.execute(
	at org.apache.activemq.transport.InactivityMonitor.writeCheck(
	at org.apache.activemq.transport.InactivityMonitor$
	at java.util.TimerThread.mainLoop(

N.B. The system was not shutting down as far as I can see. No idea what happened with our
system, we only saw this once in our logs.
Could there be a race condition when a Write check throws an exception? Since the timer is
scheduled at fixed rate, if the system was to halt for a while it may try to execute the task
a fair few times? You may get the sense I have little clue what I'm talking about :-)

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

View raw message