James.Strachan wrote:
>
> Hmm - I wonder if we should force the creation of a connection on
> startup of the consumer, to ensure things work correctly...
>
Don't know, if this helps. I tried to simulate this behavior, by using the
"failover" protocol:
<bean id="activemq"
class="org.apache.camel.component.jms.JmsComponent">
<property name="connectionFactory">
<bean
class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL"
value="failover:(tcp://127.0.0.1:41616)" />
</bean>
</property>
</bean>
But the result is the same. Looks to me, like a activemq bug, since some
instance is switching back to the default port 61616, which was not
declared:
10:42:32,768 INFO [DefaultMessageListenerContainer] Could not refresh JMS
Connection - retrying in 5000 ms
javax.jms.JMSException: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
James.Strachan wrote:
>
> Hmm - did you explicitly configure the activemq component on the
> remote side too?
>
Yes, I did. I used on both sides the same activemq component configuration:
<bean id="activemq"
class="org.apache.camel.component.jms.JmsComponent">
<property name="connectionFactory">
<bean
class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL"
value="tcp://127.0.0.1:41616" />
</bean>
</property>
</bean>
Regards,
Carsten
--
View this message in context:
http://www.nabble.com/spring-remoting-over-jms-tp14640388s22882p15201997.html
Sent from the Camel - Users mailing list archive at Nabble.com.
