[
https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483443#comment-13483443
]
Helen Huang commented on AMQCPP-405:
------------------------------------
I took out the timeout=1000 configuration from the uri, but was still able to
reproduce the problem.
The following is the code where we call cmsTemplate to receive messages. We do
set the receive timeout in the code. The value we use is 3000. Could you pleaes
do a similar test and see if you can reproduce the problem? Thanks!
if(m_cmsTemplate)
{
m_cmsTemplate->setReceiveTimeout(timeoutForThisLoop);
cms::Message* cmsMessage=NULL;
try {
cmsMessage = m_cmsTemplate->receive();
}
catch( cms::CMSException& ex) {
m_mutexForCmsTemplate.unlock();
Trace( TRACE_ERROR,
_T("Receiver::ReceiveMessage() - Caught CMSException, error message: %s, stack
trace: %s")
,CString(ex.getMessage().c_str())
,CString(ex.getStackTraceString().c_str())
);
errorCode=CMS_ERROR_CAUGHT_CMS_EXCEPTION;
break;
}
...
}
> 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
