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-328) crash found in activemqcpp when turning broker offline
Date Wed, 08 Dec 2010 22:08:01 GMT

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

Timothy Bish commented on AMQCPP-328:
-------------------------------------

I've tried to reproduce a crash in Windows XP with VS2008 and Windows 7 64bit with VS2010
as well as on Linux and I can't see to make it happen.   If you can reproduce it more reliably
then maybe you can capture it in a debugger and get a back trace on all active threads so
I can see what's going on at the time.  

It looks as if the receive thread just waits on a blocking receive forever which means you
won't ever wake up to know its time to close.  You could call receive with a timeout and check
the close flag periodically.  

The Thread class doesn't currently allow for Thread interruption as that's a rather big nut
to crack even without the concern of being in a platform independent API.  

> crash found in activemqcpp when turning broker offline
> ------------------------------------------------------
>
>                 Key: AMQCPP-328
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-328
>             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.2.4
>
>         Attachments: BrokerMonitor.zip, screenshot-1.jpg, test program.zip
>
>
> 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
program:
> (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.


Mime
View raw message