activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: Slave but worker !
Date Tue, 31 Mar 2009 18:05:38 GMT
you would need to manage the slave broker start in another bean and thread.
set the start property to false and inject the broker bean into another bean
where the broker.start() can be called in another thread.

2009/3/30 Samuel Liard <samuel@net-liard.com>

>
> Of course ! :)
> But it's not my question. Ok, slave broker is waiting... but why other
> stuff
> declare in my spring configuration are waiting to ?
>
> I just want in the same JVM (same spring configuration) a slave broker (do
> nothing, just wait master dead) and a consumer connect to the master node.
>
> But maybe it's not possible ;)
>
> Samuel
>
>
> Joe Fernandez wrote:
> >
> > A slave broker will not accept connections from clients or other brokers
> > until it becomes a master.
> >
> > Joe
> > Get a free ActiveMQ user guide at http://www.ttmsolutions.com
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Slave-but-worker-%21-tp22782932p22784453.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
http://blog.garytully.com

Open Source SOA
http://FUSESource.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message