activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Helen Huang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-328) crash found in activemqcpp when turning broker offline
Date Fri, 10 Dec 2010 02:09:02 GMT

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

Helen Huang commented on AMQCPP-328:
------------------------------------

Thank you for the feedback. We have compiled the source in VS2005. The crash is kind of hard
to reproduce. You will need to repeat the test a number of times to see it. Sometimes if you
do not see the crash, you might find the sender/main thread appears to hang in function MutexImpl::Unlock,
where the lock count value is very much high (maybe the memory is corrupted).

Also please change the number if iterations from 10,000 to 100,000 in order to catch the problem
better.

I will send yo the trace information on the threads soon.

About the receiver timeout value, we do have it in our code (1000). But it looks like the
failover transport ignores it when the broker is off. It waits forever...


> 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