You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Unico Hommes (JIRA)" <ji...@apache.org> on 2014/09/17 14:41:33 UTC

[jira] [Commented] (JCR-3811) AppendRecord should allow reattempting database insertions of journal records should the initial attempt fail

    [ https://issues.apache.org/jira/browse/JCR-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137155#comment-14137155 ] 

Unico Hommes commented on JCR-3811:
-----------------------------------

Fixed on trunk in revision 1625518.
Fixed on branch 2.8 in revision 1625542.
Fixed on branch 2.6 in revision 1625544.

> AppendRecord should allow reattempting database insertions of journal records should the initial attempt fail
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JCR-3811
>                 URL: https://issues.apache.org/jira/browse/JCR-3811
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>    Affects Versions: 2.6.5, 2.9, 2.8.
>            Reporter: Unico Hommes
>            Assignee: Unico Hommes
>             Fix For: 2.6.6, 2.8.1, 2.9
>
>
> ConnectionHelper is able to reattempt SQL statement execution should the initial attempt fail. But it needs to be able to reset all the binary input streams to do that. The input stream that is used to insert large journal records is a FileInputStream and is not resettable. Use a InputStream that is capable of being reset.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)