[
https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282555#comment-13282555
]
Helen Huang commented on AMQCPP-405:
------------------------------------
Thank you very much for your quick response Timothy! I looked at the log files
we have, and it appears that the broker was not ever turned on during the test
after the disconnection.
Also we are not using the failover protocal. Our url is:
"tcp://%MessageBrokerIP%:%MessageBrokerPort%". Could the sender thread be
blocked the same way as you have described in this case?
I read the CMS configuration web page again, I think we can probably try to
avoid the problem by using the "connection.sendTimeout" option. We will let you
know how it goes. Thanks a lot for your help!
> 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.4.1
>
> Attachments: 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
