Major Description
Periodically messages are being trapped in the store and not delivered to consumers when the broker (using JDBC Persistence adapter) loses and then restores its connection to the DB.
The issued appears to occur when the connection to the DB is lost while the message is being committed to the DB - the message is committed to the DB but the broker does not know it has been committed as it receives an exception during the commit operation.
When the DB connection is restored the message will NOT be loaded from from the store. The trapped message is NOT added to the Broker JMX statics - it is only seen by querying the DB.
The message will be loaded when the broker is restarted.