activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Helen Huang (JIRA)" <>
Subject [jira] Commented: (AMQCPP-328) crash found in activemqcpp when turning broker offline
Date Tue, 14 Dec 2010 22:58:03 GMT


Helen Huang commented on AMQCPP-328:

Could you please also give us some instructions on how to turn on the CMS logs? Thanks!

 Sometimes we saw  cmsTemplate sent out messages without any exceptions, but these messages
never reached the broker... They could have sit in a local queue, or timedout....  We had
to restart the application to overcome the issue. The CMS logging information would be very
much helpful for us to understand the problem.  Thanks!

> crash found in activemqcpp when turning broker offline
> ------------------------------------------------------
>                 Key: AMQCPP-328
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 3.2.3
>         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
>             Fix For: 3.3.0
>         Attachments:, BrokerMonitorCrash.suo, CMSMessageHandlerCOMTest.exe__PID__2008__Date__12_14_2010__Time_05_23_55PM__849__Manual
Dump.dmp, CrashHang_Report__CMSMessageHandlerCOMTest.exe__12142010173158964.mht, screenshot-1.jpg,
> We found a crash in activemqcpp when we are shutting down the message broker.  In the
meanwhile, our application is still trying to send messages to the broker, and to receive
messages from it. Could you please take a look at this problem? Much thanks for your help!

> The place of the crash appears to be in TransportFilter::Fire(Exception&) on line
49. The content of the address that the listener pointer is pointing to seems to be corrupted/garbage.
Please see the call stack in the attached screen shot for details. 
> Attached please also find a test program to reproduce the problem. Step to run the test
> (1) download and unzip test program
> (2) register GTOUD.dll
> (3) register CmsMessageHandlerCOMUD.dll
> (4) run CmsMessageHandlerCOMTest.exe
> (5) repeatedly restart activemqcpp broker. 
> (6) observe the crash

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message