Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Message-ID: <7928465.post@talk.nabble.com>
Date: Mon, 18 Dec 2006 05:13:41 -0800 (PST)
From: mers <emerson.farrugia@gmail.com>
To: activemq-users@geronimo.apache.org
Subject: Accessing failover://'s keep alive.
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hi,

I'm working on code that will use the failover:// transport in ActiveMQ 4.1
to send messages to a remote queue. In the event that all reconnects fail
(e.g. network problems), I catch the thrown JMSException in my code and
persist messages locally. When one or more brokers come back up, I transmit
the persisted messages.

In order to do this, I need to know when the brokers are back up using some
sort of keep alive mechanism. The failover:// transport uses a keep alive
mechanism to allow blocked MessageProducers to complete their sends once the
Connection they are sending on is reestablished. My question is whether my
code can access the keep alive mechanism built into the failover://
transport or whether I have to implement my own mechanism altogether.

Thanks,
Emerson


-- 
View this message in context: http://www.nabble.com/Accessing-failover%3A--%27s-keep-alive.-tf2839794.html#a7928465
Sent from the ActiveMQ - User mailing list archive at Nabble.com.