Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates
 209.85.216.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACcs02tTYnqfsD6qCniaG5UPK4z_BBmhXP1U9JzODa3Kw-Wr1g@mail.gmail.com>
References: 
 <CACcs02s2vJ7h9+mUzdDjvWXYueBkzLK8yiGEt5OGXh6rB-33=Q@mail.gmail.com>
	<CAH+vQmMzpNBu1wC7MR=VYLKg3vmmSz+ND93O5X_2=-xywxn9dA@mail.gmail.com>
	<CACcs02tTYnqfsD6qCniaG5UPK4z_BBmhXP1U9JzODa3Kw-Wr1g@mail.gmail.com>
Date: Thu, 1 Dec 2011 18:41:57 +0000
Message-ID: 
 <CAH+vQmMU9t==spac__Psj2=R0QYa1UGwsZfjMmHgQxcjtZ+6mA@mail.gmail.com>
Subject: Re: Buffering producer messages
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1

That is all good, but don't use static:(failover://) for the network
connector, just use static:(tcp:// ) and the network connector will
handle any failure by restarting the network bridge.
failover: can get in the way of network bridge recovery/restart and
leave the network bridge in limbo. It is intended for use with jms
clients, the network bridge is a little more than a plain jms client
as it multiplexes messages from many clients and monitors advisories
and control messages etc.

On 1 December 2011 10:22, Joe Carter <joe.carter@gmail.com> wrote:
> As I require persistence on the messages, I configured the embedded
> broker to use the MemoryPersistenceAdapter.
> This allows me to set the persistent flag which I presume will be
> carried forward into my remote broker which really will persist the
> message.
> My network connector using the following URI:
> static:(failover:(nio://localhost:61616)?trackMessages=true) so I
> shouldn't lose any messages from the embedded to the remote broker.
> I do realise that a failure of the process with the embedded broker
> will lose any in-flight messages that haven't made it to the remote
> broker, but for my application that risk is acceptable.
> Let me know if that doesn't do what I expect.
>
> Thanks for the help.
> Joe
>
> On 30 November 2011 16:25, Gary Tully <gary.tully@gmail.com> wrote:
>> the typical activemq way to do that is use an embeded vm broker and a
>> network connector to forward messages to the target when it can.
>> Disable persistence and it will use a memory store so it will be have
>> like a buffer.
>>
>> On 29 November 2011 16:27, Joe Carter <joe.carter@gmail.com> wrote:
>>> Hi,
>>>
>>> Does anyone know how to configure the connection factory so that it
>>> will buffer messages while there's a temporary outage to the broker?
>>> Basically the same as the "Buffered JMS client" in the IBM MQ product
>>> http://www-10.lotus.com/ldd/lewiki.nsf/dx/01022009113953AMBJANPR.htm
>>> At the moment my application receives exceptions until the connection
>>> recovers and I can't afford to block (its a soft real time app).
>>> If not I'll write my own wrapper but I'd be surprised if there's not
>>> one out there already.
>>>
>>> Thanks
>>> Joe
>>
>>
>>
>> --
>> http://fusesource.com
>> http://blog.garytully.com


-- 
http://fusesource.com
http://blog.garytully.com