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 1E9EBE267 for ; Mon, 11 Feb 2013 20:45:13 +0000 (UTC) Received: (qmail 56759 invoked by uid 500); 11 Feb 2013 20:45:12 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 56723 invoked by uid 500); 11 Feb 2013 20:45:12 -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 56714 invoked by uid 99); 11 Feb 2013 20:45:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 20:45:12 +0000 Date: Mon, 11 Feb 2013 20:45:12 +0000 (UTC) From: "Timothy Bish (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMQCPP-461) Create Thread objects that aren't started can leak their suspended thread on destroy. 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/AMQCPP-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-461. --------------------------------- Resolution: Fixed Fixed on trunk. > Create Thread objects that aren't started can leak their suspended thread on destroy. > ------------------------------------------------------------------------------------- > > Key: AMQCPP-461 > URL: https://issues.apache.org/jira/browse/AMQCPP-461 > Project: ActiveMQ C++ Client > Issue Type: Bug > Components: Decaf > Affects Versions: 3.5.0 > Reporter: Timothy Bish > Assignee: Timothy Bish > Fix For: 3.5.1, 3.6.0 > > > If a Thread object is created but its start method is never called. When destroyed the actual thread can leak if its sitting in the suspended state waiting to be started. This happens right now in the case where a task is submitted to a ThreadPoolExecutor but is rejected for some reason such as the ExecutorService already being shut down. We need to check for the suspended state on destroy and wake the thread with its cancel flag set so it shuts down normally. -- 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