Hi there,
I think this may be an Active/MQ issue, but I'm posting here too as it is
the Camel ActiveMQComponent that I'm using.
I have a broker on machine A that publishes a topic for machine B to
subscribe to. Machine A shuts down each night at 12am and powers up at 5am.
Machine B sleeps at 12am and wakes up at 5am (as distinct from powering
down/up; just in case this is relevant).
What I'm finding is that when machine B sleeps/wakes it does not appear to
be connected to the topic any longer. I have verified this by observing that
there is no ActiveMQ.Advisory.Consumer.Topic.<topicname> after about
12am (my Hyperic monitoring tool confirms this). In addition when I look at
the AMQ console on machine A after 5am, there is no connection for machine B
(where there was one the night before).
If I restart my subscriber application on machine B then all is again well.
I'm using AMQ v.5.3.1. In addition here is my Spring configuration for
subscribing for the topic:
<bean id="activeMQConnectionFactory"
class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL"
value="tcp://192.168.1.13:61616" />
</bean>
<bean id="jms-receiver"
class="org.apache.activemq.camel.component.ActiveMQComponent">
<property name="connectionFactory" ref="activeMQConnectionFactory"
/>
</bean>
Any ideas on what I may be able to do to circumvent the issue I'm seeing?
Kind regards,
Christopher
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510193p510193.html
Sent from the Camel - Users mailing list archive at Nabble.com.
