activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <>
Subject Re: jdbcPersistence behaviour
Date Mon, 12 Nov 2007 17:07:21 GMT
On 11/11/2007, ikbenben <> wrote:
> hey all,
> i've got a question regarding the behaviour of using the
> jdbcPersistenceAdaptor.  i have deployed ActiveMQ into a clustered JBoss
> 4.0.5 environment.  I basically have 2 JBoss servers, each of which has the
> ActiveMQ RAR deployed.  I've attached the broker xml file for reference:
> broker.xml
> When i start up the JBoss servers, the first server comes up correctly but
> the second jboss instance hangs during start up while it is trying to get a
> lock on the database (activemq).  when i shut down server one, the second
> instance continues and finishes the start up.  is this how it should behave?

Yes - the first broker to start is the master, it locks the database -
the others are slaves.

If you don't want the brokers to be a master/slave cluster, then just
use a different database for each broker; though then you probably
will want to network your brokers together to make a store and forward

> the reason i'm asking was i intended to deploy a EAR file in the jboss
> instance on each server which would use activemq tp send messages to other
> applications.  however, if the second instance doesn't come up ever then
> this won't work as i need to ensure i have clustering working on the EAR
> level.

So either run your master/slave brokers separately to your jboss
servers (e.g. running the bin/activemq command) or try figure out how
to do an async start in jboss, or run the brokers in separate jboss
servers? Note that the RAR can connect to a remote broker - it doesn't
need to boot up an ActiveMQ broker


Open Source SOA

View raw message