[
https://issues.apache.org/activemq/browse/AMQ-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45072#action_45072
]
Hiram Chirino commented on AMQ-1886:
------------------------------------
good catch.. I think the root cause is that the close() call in the finally
method is not really closing out the jdbc connection. On a transacted
connection if the connection is actually closed before a commit(), it should
automatically cause a transaction rollback.
Will work on a patch for this.
> Transactions used in a JDBC store WITHOUT a journal will not commit the UOW
> in an atomic operation
> --------------------------------------------------------------------------------------------------
>
> Key: AMQ-1886
> URL: https://issues.apache.org/activemq/browse/AMQ-1886
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.1.0
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 5.2.0
>
>
> The JDBC store's primary use case has always been to be used in conjunction
> with the journal. When the journal is in place it recovers any partially
> committed transaction and makes the JDBC store consistent. When the journal
> is not used, for example when you are setting up an HA solution with an HA
> JDBC database, then it has been noticed that on a DB failure you may get
> partial commits of JMS transactions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
