You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Teemu Torma (JIRA)" <ji...@apache.org> on 2009/12/04 22:01:52 UTC
[jira] Commented: (AMQCPP-271) Connection shutdown crashes if the
server went down
[ https://issues.apache.org/activemq/browse/AMQCPP-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56271#action_56271 ]
Teemu Torma commented on AMQCPP-271:
------------------------------------
I forgot to mention that this is in 3.1.0 rc1.
> Connection shutdown crashes if the server went down
> ---------------------------------------------------
>
> Key: AMQCPP-271
> URL: https://issues.apache.org/activemq/browse/AMQCPP-271
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl
> Affects Versions: 3.1
> Environment: Ubuntu Jaunty 64bit
> Reporter: Teemu Torma
> Assignee: Timothy Bish
> Fix For: 3.1
>
>
> If the activemq server is brought down while a consumer is active and not using failover transport, the connection close will result in a pure virtual method call, and if using valgrind many errors are reported.
> The problem can be easily shown with the modified example SimpleAsyncConsumer.cpp, by commenting out the exit call in onException method and by not using failover transport.
> Once modified, start the example, shutdown the activemq server and press quit in the example.
> This has worked fine at least in version 2.2.2, I did not test 3.0.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.