mq-jms-spring | assist MQ JMS integration with Spring frameworks | Object-Relational Mapping library

As has been hinted in the comments your Event class needs to be serialisable, which it does seem to be and the listener code should look something like:

From a strictly JMS perspective, when the onException method of your ExceptionListener is invoked it is up to your application to re-establish the JMS connection using ConnectionFactory.createConnection. This is a blocking call so once it return successfully then you know the connection has been re-established.

If you're delegating the JMS connection management to Spring it's unlikely you will be able to be informed about when the JMS connection is re-established. I don't see any hooks in Spring JMS for this.

This sounds like you are mixing retriable and non-retriable error handling. If you are tracking redelivers and need to send an alert, then you probably do not want to set a BOTHRESH value, and instead manage it all in your client-side code.

Recommended consumer error handling pattern:

1. If the message is invalid (ie.. bad JSON or XML) move to DLQ immediately. The message will never improve in quality and there is no reason to do repeated retries.

2. If the 'next step' in processing is down (ie. the database) reject delivery and allow redelivery delays and backout retries to kick in. This also has the benefit of allowing other consumers on the queue to attempt processing the message and eliminates the problem where one consumer has a dead path from holding up a messages.

Also, consider that using client-side consumer code to do monitoring and alerting can be problematic, since it combines different functions. If your goal is to track invalid messages, monitoring the DLQ is generally a better design pattern and it removes 'monitoring' code from your consumer code.

If you do not want your application to be considered unhealthy when JMS is down, disabling the JMS health indicator is what I would recommend. It hasn't worked for you as you have used management.endpoint.jms.enabled. The correct property to use is management.health.jms.enabled: