It is not shocking if second broker is configured as a slave. Most of the time such config are done with an external amq to keep tomee stateless Le 24 oct. 2014 21:37, "Leonardo K. Shikida" <[email protected]> a écrit :
> well, I am using BrokerXmlConfig=xbean:file... to get the properties file > > but then, here's the problem. While the first tomee starts, the second one > seems to wait for its embedded JMS to start. Since it will be a slave > server, waiting for a lock, whole tomee also waits for it to start... > > so tomee does not start. > > is that the expected behavior? > > > > [] > > Leo > > On Fri, Oct 24, 2014 at 3:39 PM, Leonardo K. Shikida <[email protected]> > wrote: > > > Hi > > > > I can run 2 tomee's using 2 external JMS servers in the failover mode, > > using a tomee.xml like this > > > > <Resource id="MyJmsResourceAdapter" type="ActiveMQResourceAdapter"> > > BrokerXmlConfig = > > ServerUrl = > > failover:(tcp://s1:61616,tcp://s2:61616)?randomize=false > > </Resource> > > > > > > If I want to start two embedded JMS servers, one in each tomee, in a > > failover mode, what's the syntax? I've been trying this > > > > <Resource id="MyJmsResourceAdapter" type="ActiveMQResourceAdapter"> > > BrokerXmlConfig = broker:(tcp://s1:61616)?persistent=true > > ServerUrl = > > failover:(tcp://s1:61616,tcp:/s2:61616)?randomize=false > > DataSource = MyJmsDataSource > > </Resource> > > > > where MyJmsDataSource points to some JDBC resource (must be the same for > > both). Of course, the other tomee declares its broker in the > > "BrokerXmlConfig" > > > > But something is not right. I feel I am missing something. Is this the > > right syntax? > > > > TIA > > > > Leo > > >
