You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2018/11/13 15:05:00 UTC
[jira] [Commented] (OAK-7342) RDBDocumentStore: missing rollback
after delete failures
[ https://issues.apache.org/jira/browse/OAK-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685342#comment-16685342 ]
Julian Reschke commented on OAK-7342:
-------------------------------------
trunk: [r1826833|http://svn.apache.org/r1826833]
1.8: [r1846518|http://svn.apache.org/r1846518]
> RDBDocumentStore: missing rollback after delete failures
> --------------------------------------------------------
>
> Key: OAK-7342
> URL: https://issues.apache.org/jira/browse/OAK-7342
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: rdbmk
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, candidate_oak_1_6
> Fix For: 1.9.0, 1.10, 1.8.10
>
>
> There are a few places where after an exception, the connections isn't rolled back (harmless, if the connection pool does it for us).
> This can be detected when running with PostgreSQL and setting
> {noformat}
> -Dorg.apache.jackrabbit.oak.plugins.document.rdb.RDBConnectionHandler.CHECKCONNECTIONONCLOSE=true
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)