There's been no failover. Other routes continue to have their consumers working normally and messages still arrive normally from the producers.
The issues are with camel in the master ActiveMQ instance. By the configuration I posted, camel has no knowledge that it is deployed into a master/slave configured ActiveMQ, and in particular no knowledge of the IP address of the slave broker. With the vm protocol, wouldn't the routes get built independently in both the master and the slave when each starts? I'm pretty sure we've tested failover with our configuration. James.Strachan wrote: > > After this failure, has the master/slave failed over? Its not clear if > its the camel in the master or camel in the slave which is having > issues? > > To avoid such issues I'd suggest using the broker URL > > failover:tcp://master:61616,tcp://slave:61616 > > if you want both sets of camel routes to keep running. > > Note that the vm transport ignores the master/slave configuration in > ActiveMQ; so the camel route will not failover to the new master > > 2008/12/18 bwtaylor <bryan_w_tay...@yahoo.com>: >> >> We run master slave ActiveMQ, but camel is embedded in activemq, so Camel >> is >> not aware of the other instance. Our consumers are created by the route >> builders using "activemq:" endpoints, via the connection factory using >> the >> following spring configuration: >> >> <bean id="activemq" >> class="org.apache.activemq.camel.component.ActiveMQComponent"> >> <property name="connectionFactory" ref="activeMqConnectionFactory" >> /> >> </bean> >> >> <bean id="activeMqConnectionFactory" >> class="org.apache.activemq.spring.ActiveMQConnectionFactory" >> lazy-init="true"> >> <property name="brokerURL" value="vm://radar-broker" /> >> </bean> >> >> The brokerURL value refers to the brokerName we give via the <broker> >> element in activemq.xml. >> >> >> Claus Ibsen-2 wrote: >>> >>> Can you show the activemq configuration of the consumers? >>> Are you using the failover transport, that might help? >>> >>> But try to get the attention of James he is export on AMQ as well. >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Activemq-Consumers-Vanish-tp21062377s22882p21081480.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> >> > > > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://fusesource.com/ > > -- View this message in context: http://www.nabble.com/Activemq-Consumers-Vanish-tp21062377s22882p21130242.html Sent from the Camel - Users mailing list archive at Nabble.com.