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] Updated: (AMQCPP-328) crash found in activemqcpp when turning broker offline
Date Mon, 22 Nov 2010 16:31:24 GMT

     [ https://issues.apache.org/activemq/browse/AMQCPP-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Helen Huang updated AMQCPP-328:
-------------------------------

    Attachment: BrokerMonitor.zip

Please use the attached BrokerMonitor program to recreate the issue. Thank you very much for
your help!

This program has three major components:
(1) BrokerMonitor (BrokerMonitor.cpp) - BrokerMonitor trys to determine the broker's status
(online/offline). It opens a thread, sends heart beat messages to the broker and receives
them from it.  If the broker appears to be offline, BrokerMonitor would recreate its cmsTemplate
for future reconnection.

(2) Sender (Main.cpp) - Sends 10000 messages

(3) Receiver (Receiver.cpp) - Opens a thread, and receives message. It looks at the broker's
status, and recreates cmsTemplate for reconnection when needed.

Note that both BrokerMonitor and Receiver recreate cmsTemplate. This is a workaround for an
issue we opened earlier https://issues.apache.org/activemq/browse/AMQCPP-316 . That issue
will be resolved in activemqcpp release 3.3.  However we would like to stick to 3.2.x for
now if possible, because we are at the very end of an upcoming release of our own product.




> crash found in activemqcpp when turning broker offline
> ------------------------------------------------------
>
>                 Key: AMQCPP-328
>                 URL: https://issues.apache.org/activemq/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