Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 8 Nov 2012 21:18:13 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <609904035.88865.1352409493163.JavaMail.jiratomcat@arcas>
In-Reply-To: <1606780758.13546.1337810503088.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (AMQCPP-405) CMS sender thread hangs after
 restarting broker
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493497#comment-13493497 ] 

Timothy Bish commented on AMQCPP-405:
-------------------------------------

Not really sure when I'll have time to navigate my way through all that in order to try and reproduce it.  Does this produce something that allows for stepping into the code?

Looking at the stack trace its hard to say for sure what going on since MS tools don't give you line numbers so I can't really tell which critical section is being waited on here.  My initial thought is that its the library global lock which means that the library shutdown method was called before all the CMS object had finished and been disposed of but that's just a guess haven't really been able to figure out the application code and I'm not really a COM person so not sure the lifecycle here. 
                
> CMS sender thread hangs after restarting broker
> -----------------------------------------------
>
>                 Key: AMQCPP-405
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-405
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 3.4.1
>         Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1
>            Reporter: Helen Huang
>            Assignee: Timothy Bish
>            Priority: Critical
>             Fix For: 3.5.0
>
>         Attachments: CMS_Test_Tool.7z, CrashHang_Report__CMSMessageHandlerCOM-TestMultipleSendersReceivers.exe__11072012173926312.mht, CrashHang_Report__CMSMessageHandlerCOM-TestReceiver.exe__10242012114621213.mht, CrashHang_Report__CMSMessageHandlerCOM-TestSender_exe__1001201211243973.mht, CrashHang_Report__CMSMessageHandlerCOM-TestSender_exe__1001201220471946.mht, CrashHang_Report__CMSMessageHandlerCOM-TestSender_exe__10022012152424484.mht, CrashHang_Report__CMSMessageHandlerCOM-TestSender_exe__10032012172730765.mht, CrashHang_Report__PID_2832__05232012143544484.mht, CrashHang_Report__SCOTApp.exe__10272012120620437.mht, CrashHang_Report__SCOTApp_exe__11012012195321234.mht
>
>
> The sender thread in CMS hangs after we retarted the message broker.
> The thread is 548 in the attached dump file. 
> This is a critical issue that blocks the release of our product that is scheduled in a few days. We hope you can resolve it soon. Really appreciate your help!

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