activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-316) Unable to receive any messages after re-starting message broker
Date Mon, 13 Sep 2010 19:50:40 GMT

    [ https://issues.apache.org/activemq/browse/AMQCPP-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61795#action_61795
] 

Timothy Bish commented on AMQCPP-316:
-------------------------------------

The TCP Transport does NOT reconnect, so without looking at the CMSTemplate code I'd guess
there's a handler in there somewhere that's grabbing the exception and reconnecting on each
send.  I didn't write any of that code so not sure what it does in these circumstances.

The failover transport has a timeout option that will cause it to give up on a send request,
so you call would throw an exception when the timeout occurs.

> 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.2
>         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.3
>
>         Attachments: 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.


Mime
View raw message