[
https://issues.apache.org/jira/browse/AMQ-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea updated AMQ-4934:
---------------------------------
Fix Version/s: 5.9.1
> JDBCPersistenceAdapter: queue messages trapped in store when DB connection is
> lost and restored
> -----------------------------------------------------------------------------------------------
>
> Key: AMQ-4934
> URL: https://issues.apache.org/jira/browse/AMQ-4934
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.9.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.9.1, 5.10.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
