activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: Messages not delivered after failover.
Date Tue, 15 May 2012 21:07:01 GMT
Gary wrote:
> ... you may need to configure keep alive on the broker transport connector ...

I had tried setting that on the broker transport that the client uses, but saw zero traffic
between the client and the broker. I'm guessing that it is only useful when set on the broker's
end, which is what I think you're suggesting? I can't restart the broker right now, as most
of my clients aren't configured to use failover yet, and they'll just die. But this Saturday,
I have a maintenance window to update to the latest ActiveMQ. I'll add that then and configure
my other clients to use failover.

I'll look into checking via JMX. I'm very new to Java and JMS (about 3 weeks worth of experience),
but learning fast. :)

Thank you for your reply!


-----Original Message-----
From: Gary Tully []
Sent: Tuesday, May 15, 2012 4:57 PM
Subject: Re: Messages not delivered after failover.

the client sees the disconnect due to the firewall, but does the broker see the same disconnect?
you may need to configure keep alive on the broker transport connector to ensure that it sees
the client disconnect.
You can check via jmx (jconsole), to verify that the consumer goes away. If it remains, then
prefetched messages will still be inflight and not visible to other consumers till the connection
is closed.
The inflight count on the destination will also give an indication if this is the case.

On 15 May 2012 20:39,  <> wrote:
> One of the two issues has been resolved. The connection being reset was due to a firewall,
between the broker and consumer, closing port 61616 due to inactivity. We've had the folks
who maintain the firewall change its configuration so that it no longer does that.
> I'm still very troubled by the fact that messages could no longer be delivered after
a failover event though.

Subject to local law, communications with Accenture and its affiliates including telephone
calls and emails (including content), may be monitored by our systems for the purposes of
security and the assessment of internal compliance with Accenture policy.

View raw message