Your exception seems to indicate that you haven't configured your
ActiveMQConnectionFactory correctly. What the error shows is that you
have connected it to:
tcp://10.0.0.97:61616
What will happen in that configuration is that when the connection
drops, the connection factory will remain in a
I have removed all transaction handling both from the route and from the
ActiveMQ connection factory. I still see:
09/Feb/2015 15:58:40,159- DefaultErrorHandler: Failed delivery for
(MessageId: ID-ngw-smtp-01-50108-1423497456378-0-7 on ExchangeId:
ID-ngw-smtp-01-501
08-1423497456378-0-11). On deli
Hi
If you use ActiveMQ you may need to turn off asyncSend
http://activemq.apache.org/async-sends.html
On Mon, Feb 9, 2015 at 4:20 PM, James Green wrote:
> We have a route from a REST endpoint into a JMS (InOnly) endpoint.
>
> We took down the broker to see what would happen. Turns out HTTP clien
We have a route from a REST endpoint into a JMS (InOnly) endpoint.
We took down the broker to see what would happen. Turns out HTTP clients
hang waiting for a response (for several minutes) while a load of stack
traces are logged by Camel:
09/Feb/2015 15:07:52,677- DefaultErrorHandler: Failed del
