We are using Apache Camel with ActiveMQ in a microservice architecture in a growing system of integration solutions. I was wondering how each service should react when they are unable to connect to the message queue, or if this should be handled at all.
As the system is right now each service logs an exception for each reconnect attempt if the message queue broker is unreachable. This seems very sub-optimal. Are there any already implemented solutions or other smart suggestions that can handle this? We run 1 non-clustered broker on localhost, so if the broker is uncreachable, it is most likely caused by the service containing the broker actually having crashed and would not be up until someone manually restarts the entire servlet container (jetty in this case), which would most likely take minutes at least. And by the time someone restarts it the log files would have countless JMS connection exceptions.