[
https://issues.apache.org/jira/browse/AMQCPP-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971548#action_12971548
]
Helen Huang commented on AMQCPP-328:
------------------------------------
Thanks for the feedback on the logging question.
Also I have noticed the VS2005/VS2008 project files that come with the
activemqcpp 3.2.x releases do not have any unicode configurations. Also the
libraries are expecting std::string to be passed in as parameters.
My question is, if my application is unicode, can I still use the ANSI build of
the activemqcpp libs/dlls safely, if all the parameters passed into activemqcpp
are converted to std::string (payload of the message will be converted to UTF-8
bytes). I think the answer is yes, but I think I should double check with you
to make sure.
Thank you very much for your help!
> 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.3.0
>
> Attachments: BrokerMonitor.zip, 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, 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.
