[
https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467374#comment-13467374
]
Helen Huang commented on AMQCPP-405:
------------------------------------
I have tested the new snapshot and was not able to recreate the hang. However,
I got a crash when I restarted the message broker. Attached please find a full
dump.
The code that failed is in ActiveMQConnection.cpp, at line
"this->config->transport->stop();". this->config->transport appeared to be null
at the crash.
virtual void run() {
try {
// Mark this Connection as having a Failed transport.
this->connection->setFirstFailureError(ex);
try{
this->config->transport->stop();
} catch(...) {
}
this->config->brokerInfoReceived->countDown();
// Clean up the Connection resources.
this->connection->cleanup();
synchronized(&this->config->transportListeners) {
Pointer< Iterator<TransportListener*> > iter(
this->config->transportListeners.iterator() );
while( iter->hasNext() ) {
try{
iter->next()->onException(ex);
} catch(...) {}
}
}
} catch(Exception& ex) {}
}
};
> 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-TestSender_exe__1001201211243973.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
