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.226 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=RY/9GyOhWW6jjJ/IwQKxww5Iyz47CKJhPAbQuprpMVyxSyjd/dlDYtA/aiDW0h/HslUbU6vZQzujiNpmLN6L+NXspx4C67AztUKECQEpHfqtty2GPNQg9EdYUGBVMrCFAvutohH92hExtaUa53lWoQ4H3awMBeIfJwSQGWr6PoM=
Message-ID: <ec6e67fd0706120107m583d3c59kbc51aa29182ce3b3@mail.gmail.com>
Date: Tue, 12 Jun 2007 09:07:24 +0100
From: "James Strachan" <james.strachan@gmail.com>
To: users@activemq.apache.org
Subject: Re: Master/Slave on Weblogic
In-Reply-To: <11070252.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <11068583.post@talk.nabble.com> <11070252.post@talk.nabble.com>

On 6/11/07, eta <eric@ultracode.com> wrote:
>
> I've been messing with the JDBC database locker code recently, and yes, it
> will work as you described.  The default database locker service start()
> method will not return until it has acquired the lock, indicating that it is
> the master broker.
>
> I'm not sure what the recommended way around this would be, but what I would
> do would be to run the BrokerService.start() method in a separate thread
> from my servlet init() or service() methods.  This will at least allow the
> servlet to fully deploy even though the broker has not yet fully initialized
> because it is a slave.

Eric's exactly right; currnently the starting of a broker in
master/slave is synchronous which would block the calling thread (such
as a web app or Spring configuration) until it becomes the master.

We need a way to allow the starting of the broker to be asynchronous
to avoid blocking the calling thread. I've created a JIRA for this
https://issues.apache.org/activemq/browse/AMQ-1273

In the mean time; another work around is to run the broker as a
separate deployment unit in your server (e.g. in a separate web app)

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