jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1825) DBDataStore doesn't support concurrent reads
Date Tue, 21 Oct 2008 11:59:44 GMT

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

Thomas Mueller commented on JCR-1825:


You are right, this part of the code doesn't do any more what it's supposed to do. There is
another problem: it doesn't work if the stream is null. Also some of the DbResources methods
are not not used and should be removed.

I am currently working on another patch, I will attach it in an hour or so to this bug.

Thanks for finding this problem!


> DBDataStore doesn't support concurrent reads
> --------------------------------------------
>                 Key: JCR-1825
>                 URL: https://issues.apache.org/jira/browse/JCR-1825
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.5.0
>            Reporter: Przemo Pakulski
>             Fix For: 1.5.0
> My understanding is that setting parameter copyWhenReading to true should allow concurrent
reads by spooling binary property to temporary file and free database resources (connection)
immediately to make it available for other threads.
> After applying patch for JCR-1388, DBDataStore doesn't support concurrent reads anymore,
resultSet is kept open and db connection is blocked until the stream is read and closed. When
copyWhenReading is set to true db connection should be released immediately, this is the reason
i guess why temporary file is used.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message