Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 12 Feb 2013 22:41:15 +0000 (UTC)
From: "John Rocha (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12632107.1360708533814.280827.1360708875386@arcas>
In-Reply-To: <JIRA.12632107.1360708533814@arcas>
References: <JIRA.12632107.1360708533814@arcas>
Subject: [jira] [Updated] (AMQCPP-462) Producer aborts/core dump during
 ActiveMQCPP::shutdownLibrary()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQCPP-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Rocha updated AMQCPP-462:
------------------------------

    Attachment: CoreInfo.txt
                core-SimpleProducer..9541
                SimpleProducer.exe
                SimpleProducer.cpp

Uploaded the SimpleProducer.cpp file that I used to reproduce the problem. Uploaded the SimplerProducer.exe and core file. Couldn't upload the AMQ-CPP library as it is too large. Also uploaded the CoreInfo.txt file that has the basic "where" output from GDB for the core file.
                
> Producer aborts/core dump during ActiveMQCPP::shutdownLibrary()
> ---------------------------------------------------------------
>
>                 Key: AMQCPP-462
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-462
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Decaf
>    Affects Versions: 3.5.0
>         Environment: This has been observed on both RedHat 5.8 and SUSE SLES10
> 32bit Linux machines. We are linking with apr version 1.4.2 and apri-util version 1.3.9
>            Reporter: John Rocha
>            Assignee: Timothy Bish
>              Labels: abort, activemq, core, crash, decaf, shutdown
>             Fix For: 3.5.1
>
>         Attachments: CoreInfo.txt, core-SimpleProducer..9541, SimpleProducer.cpp, SimpleProducer.exe
>
>
> Producer aborts/core dump during ActiveMQCPP::shutdownLibrary()
> We recently upgrade from the AMQ-CPP-Client from 3.4.5 to 3.5.0. After doing
> this we found that we would get aborts and core files when shutting down the
> proces.
> I've also been able to reproduce the problem with the simple consumer, which
> equates to basically.
> # Invoke the initializeLibrary() routine.
> # Print the library version and CMSX properties
> # Invoke shutdownLibrary()
> When I link against the 3.4.5 library there is no abort/core. When I link
> against 3.5.0 we abort/core.
> +Environments:+ This has been observed on both RedHat 5.8 and SUSE SLES10
> 32bit. We are linking with apr version 1.4.2 and apri-util version 1.3.9
> I've attached gdb output as well as the modified SimpleProducer.cpp that I see
> the problem with.
> {panel:title=It works with the previous version}
> %>  SimpleProducer.exe 
> =====================================================
> Starting the example with version 3.4.4:
> -----------------------------------------------------
> 0: JMSXGroupID
> 1: JMSXGroupSeq
> 2: JMSXDeliveryCount
> 3: JMSXProducerTXID
> -----------------------------------------------------
> Finished with the example.
> =====================================================
> {panel}
> \\
> {panel:title=It fails with 3.5.0}
> ----------------------------------------
> %>  SimpleProducer.exe
> =====================================================
> Starting the example with version 3.5.0:
> -----------------------------------------------------
> 0: JMSXGroupID
> 1: JMSXGroupSeq
> 2: JMSXDeliveryCount
> 3: JMSXProducerTXID
> -----------------------------------------------------
> Finished with the example.
> =====================================================
> terminate called after throwing an instance of 'decaf::lang::exceptions::RuntimeException'
>   what():  Failed to Lock OS Mutex
> Abort (core dumped)
> {panel}

--
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