Camel route does not shut down due to ActiveMQ failover transport not finishing

Solution Verified - Updated -

Issue

A Camel route that uses the ActiveMQ failover: or discovery: transport to connect to an ActiveMQ broker may fail to shut down if the transport gets stuck in reconnecting to the broker.
Logging output suggests the Camel route is shutting down as per the following logging

INFO  | Thread-57        | BlueprintCamelContext   | 119 - org.apache.camel.camel-core - 2.17.0.redhat-630347 | Apache Camel 2.17.0.redhat-630347 (CamelContext: camel-jms-localtx-demo) is shutting down
INFO  | Thread-57        | DefaultShutdownStrategy | 119 - org.apache.camel.camel-core - 2.17.0.redhat-630347 | Starting to graceful shutdown 1 routes (timeout 300 seconds)

... but it never prints the line that the Camel route has fully shut down.
Instead it keeps logging

WARN  | ActiveMQ Task-1  | FailoverTransport       | 112 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-630347 | Failed to connect to [] after: XX attempt(s) continuing to retry.

Environment

  • Fuse 6.3
  • Camel
  • camel-jms component
  • ActiveMQ failover: or discovery: transport

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.