From dev-return-34386-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Fri Nov 2 18:27:13 2012 Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9CBB3D59B for ; Fri, 2 Nov 2012 18:27:13 +0000 (UTC) Received: (qmail 29803 invoked by uid 500); 2 Nov 2012 18:27:13 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 29758 invoked by uid 500); 2 Nov 2012 18:27:13 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 29603 invoked by uid 99); 2 Nov 2012 18:27:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2012 18:27:13 +0000 Date: Fri, 2 Nov 2012 18:27:13 +0000 (UTC) From: "Timothy Bish (JIRA)" To: dev@activemq.apache.org Message-ID: <1818988253.61878.1351880833208.JavaMail.jiratomcat@arcas> In-Reply-To: <2069072732.61633.1351879633113.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (AMQ-4156) Inactivity monitor rejected from thread pool MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489631#comment-13489631 ] Timothy Bish commented on AMQ-4156: ----------------------------------- I looks like there is a tiny window in which its possible that a write check task could be fired after the static ExecutorService has been shutdown because all connections closed and the class attempts to close down that service until its needed again. I don't think it will have any serious side effects as far as I can see. > Inactivity monitor rejected from thread pool > -------------------------------------------- > > Key: AMQ-4156 > URL: https://issues.apache.org/jira/browse/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 > Labels: concurrency > > 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(ThreadPoolExecutor.java:2013) > at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:816) > at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1337) > at org.apache.activemq.transport.InactivityMonitor.writeCheck(InactivityMonitor.java:147) > at org.apache.activemq.transport.InactivityMonitor$2.run(InactivityMonitor.java:113) > at org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask.java:33) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > ] > 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: http://www.atlassian.com/software/jira