a mechanism is required to shut the connections down across all the MDB instances of the same kind, when one instance caught up with a RuntimeException. ideally, we should be able to configure a retry value. which enables the MDB instances to retry a specified number of times before shutting down the connections as described and removing all the MDB instances from the pool.

importantly, we should be able to restart this service via JMX console. if this RuntimeException is triggered by a corrupted message, it should get moved to the DLQ unless we specify a unique Queue to move such messages.