activemq-dev mailing list archives

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


Timothy Bish commented on AMQCPP-316:

Unknown as to how long it would take to fix.  In case you didn't know, each time the CMSTemplate
get an exception in any of its methods it destroys the Connection, the next time you use it
a new Connection will be created, there appears to be some gaps in the code for dealing with
the cleanup when failover transport is used, but even if those are fixed, what you end up
with would be a large number of Connections being created and destroyed as the send method
times out every 3 seconds.  

If you run the app a couple of times and kill the broker after the first send cycle you will
see that the time between send calls when the broker is down is not anywhere near 3 seconds
because each attempt tries to create a new Connection that must first spin up all the internal
objects and then the Failover transport logic kicks in to connect and deal with failing connection
attempt which results in a very long wait for the Send method to times out as the Connection
is essentially blocked until a new connection is fully established.  

> Unable to receive any messages after re-starting message broker
> ---------------------------------------------------------------
>                 Key: AMQCPP-316
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>         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
>         Attachments:,
> 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.

View raw message