Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (herse.apache.org: domain of james.strachan@gmail.com
 designates 66.249.82.239 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=B1D04VoLfT+jy07dnwGy9VqCQrr1Oqyo/ZrJDBOx+vL5KZRPbj3YCnusYuut0TJ7gmsoXGHZ/LrNOQS9eiDUWtotdRurZtpkJDAa0INTXhS5Qfga++alv/dixziCIATGV1/UOn7uAzcHcLMTpgl7h254RNFw9wJtq8ABis+NK2I=
Message-ID: <ec6e67fd0705090824i6cbb659u1080925ff23224ea@mail.gmail.com>
Date: Wed, 9 May 2007 08:24:15 -0700
From: "James Strachan" <james.strachan@gmail.com>
To: users@activemq.apache.org
Subject: Re: Possible to Trade an In-Memory Queue between producer instances
 with embedded brokers?
In-Reply-To: <68B9548ED9F8A341B21CDB320655D613026FE6DA@mercury.nmwco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <68B9548ED9F8A341B21CDB320655D613026FE6DA@mercury.nmwco.com>

On 5/9/07, Chris Hofstaedter <chrish@nmwco.com> wrote:
> I'm using 4.0.2 on various Windows machines.
>
>
>
> I've got a producer with an embedded broker with a
> MemoryPersistenceAdapter wrapped in a Log4J appender.  At times, the
> log4j.xml file may change in ways that affect the way the
> producer/embedded broker are configured.  When the change is detected,
> Log4J will destroy and recreate the appender instance.  This results in
> all of my in-queue messages being lost.
>
>
>
> Unfortunately, making the embedded broker actually persist to disk not
> an option for me.
>
>
>
> I'd like to find a way to swap the local memory queue from the embedded
> broker associated with the old producer instance to the one associated
> with the new (after config change) producer instance.

By default when using the vm:// transport the broker is started up
when the first connection is created; then destroyed when the last
connection closes. If you don't want that - e.g. you want to run an
embedded broker for the duration of your process - just explicitly
create one up front on startup...

http://activemq.apache.org/how-do-i-embed-a-broker-inside-a-connection.html

-- 
James
-------
http://macstrac.blogspot.com/