[
https://issues.apache.org/jira/browse/JCR-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643222#action_12643222
]
Jukka Zitting commented on JCR-1825:
------------------------------------
Instead of tweaking the copyWhenReading workaround (which disables one of the
main benefits of the data store, i.e. the ability to access a binary property
without intermediate copies being created), I'd simply remove the
maxConnections limit from the connection pool.
> 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
>
> Attachments: patch.txt, patch2.txt
>
>
> 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.
