[
https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483510#comment-13483510
]
Timothy Bish commented on AMQCPP-405:
-------------------------------------
I think I've managed to reproduce what you are seeing, will see if I can get to
the bottom of it. If the other crash issues are truly resolved then you could
run without failover and the template should just create a new connection once
the broker gets back online. Obviously you'd need to test that pretty
carefully on your end to see if I managed to fix the earlier problems you were
seeing.
As for the wchar_t issue did you build both library and app with the same
setting for treating wchar_t as a native type? I would need to be built the
same for both to work correctly. Otherwise I'll need to look further, I didn't
have much time to test the fix I put in for that, you should open a new issue
to track it if its still happening so I can ensure I get around to that.
> CMS sender thread hangs after restarting broker
> -----------------------------------------------
>
> Key: AMQCPP-405
> URL: https://issues.apache.org/jira/browse/AMQCPP-405
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl
> Affects Versions: 3.4.1
> 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
> Priority: Critical
> Fix For: 3.5.0
>
> Attachments:
> CrashHang_Report__CMSMessageHandlerCOM-TestReceiver.exe__10242012114621213.mht,
> CrashHang_Report__CMSMessageHandlerCOM-TestSender_exe__1001201211243973.mht,
> CrashHang_Report__CMSMessageHandlerCOM-TestSender_exe__1001201220471946.mht,
> CrashHang_Report__CMSMessageHandlerCOM-TestSender_exe__10022012152424484.mht,
> CrashHang_Report__CMSMessageHandlerCOM-TestSender_exe__10032012172730765.mht,
> CrashHang_Report__PID_2832__05232012143544484.mht
>
>
> The sender thread in CMS hangs after we retarted the message broker.
> The thread is 548 in the attached dump file.
> This is a critical issue that blocks the release of our product that is
> scheduled in a few days. We hope you can resolve it soon. Really appreciate
> your help!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
