[
https://issues.apache.org/activemq/browse/AMQCPP-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62057#action_62057
]
Timothy Bish commented on AMQCPP-316:
-------------------------------------
Would need to know a bit more about the scenario that you were testing in. Was
there a broker running and you killed it, or was there nothing running when you
started your app?
In general you can assume that setting any timeout option in CMS to zero means
wait forever, not don't wait. A zero timeout on the failover transport doesn't
really make any sense, every very small one's don't really make much sense
since you are essentially making it fail before it ever has a chance to
reconnect, in which case, why use failover. When not using the CMSTemplate
code you could try a again using the same connection but in CMSTemplate once
that exception gets thrown the Whole Connection / Session / Producer stack gets
torn down and then a new Connection / Session / Producer etc gets recreated on
the next call to send, so its not something I'd think you'd want to do all that
often.
> Unable to receive any messages after re-starting message broker
> ---------------------------------------------------------------
>
> Key: AMQCPP-316
> URL: https://issues.apache.org/activemq/browse/AMQCPP-316
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl
> Affects Versions: 3.2.0, 3.2.1, 3.2.2, 3.2.3
> 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.2.4, 3.3.0
>
> Attachments: ReconnectionTest-new.zip, ReconnectionTest.zip
>
>
> We developed two applications that use CmsTemplate to send and receive
> messages. The sender application is called MessageSender, and the receiver
> application is called MessageListener. We found that the MessageListener is
> unable to receive any messages after we re-start the message broker.
> The followings are the steps to recreate the problem:
> (1) start the activemq message broker,
> (2) start MessageListener and MessageSender, and observe that messages are
> being sent and received successfully.
> (3) stop the message broker without stopping MessageListener and
> MessageSender. Wait for a while (for about a minute or two)
> (4) start the message broker again.
> We expect we can send and receive messages successfully after step (4), but
> the MessageListener can never receive any messages any more. Also from the
> activemq admin page, we find that the consumer of the topic is gone. We did
> the test with url "?keepAlive=true&wireFormat.maxInactivityDuration=0", but
> it did not work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
