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 49C89EDF2 for ; Mon, 4 Feb 2013 19:56:13 +0000 (UTC) Received: (qmail 72999 invoked by uid 500); 4 Feb 2013 19:56:12 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 72949 invoked by uid 500); 4 Feb 2013 19:56: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 72869 invoked by uid 99); 4 Feb 2013 19:56:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2013 19:56:12 +0000 Date: Mon, 4 Feb 2013 19:56:12 +0000 (UTC) From: "Jeffrey B (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMQCPP-452) Shutdown causing core dump in 3.5.0 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-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey B resolved AMQCPP-452. ------------------------------ Resolution: Not A Problem > Shutdown causing core dump in 3.5.0 > ----------------------------------- > > Key: AMQCPP-452 > URL: https://issues.apache.org/jira/browse/AMQCPP-452 > Project: ActiveMQ C++ Client > Issue Type: Bug > Components: Decaf > Affects Versions: 3.5.0 > Environment: HPUX 11.31 > Reporter: Jeffrey B > Assignee: Timothy Bish > Priority: Critical > Labels: shutdown, thread > Attachments: amqsms.cpp > > Original Estimate: 24h > Remaining Estimate: 24h > > Whenever a thread is created in my receiver program, The use of the activemq::library::ActiveMQCPP::shutdownLibrary(); causes a core dump after my return 0; statement > It does not happen on my sender after applying patch for a similar issue, and this is almost identical, so I can not find the difference. > The cause is trying to lock a null mutex in the function Threading.cpp::attachToCurrentThread(). This gets called only once in my sender program, during the activemq::library::ActiveMQCPP::initializeLibrary(); call, but it gets called twice in my receiver program, once in the same place and then after the return 0; line. At that point library->globalLock is NULL. > Will attach my source in a moment, but I have literally taken it down to the bare minimum so that it has no function. -- 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