[
https://issues.apache.org/activemq/browse/AMQCPP-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQCPP-332.
-------------------------------
Resolution: Working as Designed
As far as I can tell this is working exactly as its supposed to, the
CmsTemplate will throw exceptions when the Connection fails, the next call will
create a new connection and as long as that doesn't fail then it will behave
normally again. If you want to have the sends not fail then you'd need to use
the FailoverTransport so that the connection is re-established underneath the
CmsTemplate object.
> First send after we restart broker seems to always get a CmsException
> ---------------------------------------------------------------------
>
> Key: AMQCPP-332
> URL: https://issues.apache.org/activemq/browse/AMQCPP-332
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl
> Affects Versions: 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
> Fix For: 3.2.4
>
> Attachments: BrokerMonitor2.zip
>
>
> First send after we restart broker seems to always get a CmsException.
> Steps to recreate the problem:
> (1) download and unzip the attached test program: BrokerMonitor2.zip. This
> program is very similar to the test program for jira item 328 with just a few
> modifications. (https://issues.apache.org/activemq/browse/AMQCPP-328)
> (2) Start broker
> (3) Run the test program. The test program will iterate for 10000 times. In
> each iteration, it will first send out a message, and then prompt you to
> enter a char to continue. Please do that and make sure that the first a few
> messages are sent without any problems.
> (4) Restart broker. Wait for a while, Maybe 2-5 mins.
> (5) Enter a char for the test program to continue. Observe that the next send
> message gets a CmsException with the message "Channel was inactive for too
> long"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
