[jira] [Resolved] (AMQ-4934) JDBCPersistenceAdapter: queue messages trapped in store when DB connection is lost and restored

["Dejan Bosanac (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac resolved AMQ-4934.
--------------------------------

    Resolution: Fixed

The problem can happen when JDBC driver throw SQLEcxeption after it stores a message in the database. In that case we need to reset the cursor before we restore the transports.

This is now fixed on the trunk

> 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.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.1.4#6159)