activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQCPP-405) CMS sender thread hangs after restarting broker
Date Mon, 29 Oct 2012 19:32:12 GMT

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

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

Updated the SNAPSHOT of 3.5 to include all the latest tweaks and fixes.

If you want to look on your end to see if you can find the trouble then there's only two scenarios
that I can think of that could be happening since you aren't using failover.  Either the code
isn't detecting the connection loss which is odd since the inactivity monitor should be kicking
in after 30 seconds or so and figuring out that the connection is idle.  Or there is a deadlock
somewhere in the onException handling that causing the code to hang someplace.  For that you'd
need to capture stack traces or stop in the debugger to examine each thread to see if any
are stuck waiting in a deadlock on some resource.  possiblely in a lock someplace in between
onException processing and the CMSTemplate calling connection.close().
                
> 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: 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
>
>
> 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

Mime
View raw message