activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Helen Huang (JIRA)" <>
Subject [jira] [Commented] (AMQCPP-405) CMS sender thread hangs after restarting broker
Date Thu, 08 Nov 2012 14:13:12 GMT


Helen Huang commented on AMQCPP-405:

Hi Timothy,

I created a test tool and did some tests with the snapshots that you uploaded on Oct 29th
and Nov 5th. I found an access violation when restarting message broker. The function envolved

void PlatformThread::lockMutex(decaf_mutex_t mutex) {

File is:activemq-cpp\src\main\decaf\internal\util\concurrent\windows\PlatformThread.cpp

I will upload the test program soon.

> CMS sender thread hangs after restarting broker
> -----------------------------------------------
>                 Key: AMQCPP-405
>                 URL:
>             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:

View raw message