Gary Tully wrote: > > 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. >
Very good idee ! Unfortunately the property start of org.apache.activemq.xbean.BrokerFactoryBean didn't work. (true or false broker start) It's not "broker.start();" that start broker but the line 85 : context = new ResourceXmlApplicationContext(config, parentContext); Maybe because I use the config property like : <property name="config" value="classpath:activemqSlave.xml" /> So I put all code of afterPropertiesSet() in another thread and it's work well ! Thanks a lot Samuel -- View this message in context: http://www.nabble.com/Slave-but-worker-%21-tp22782932p22825174.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
