[
https://issues.apache.org/jira/browse/JCR-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Esteban Franqueiro updated JCR-1388:
------------------------------------
Attachment: JCR-1388-datastore-concurrent-reads.4.patch
Ok, here's a new take at it. I hope I resolved all the issues you pointed out.
> DbInputStream.mark and reset are synchronized, but nothing else in this
> class, why?
I followed the pattern used in InputStream and FilterInputStream.
Regarding the finalizer, I removed it, but I think that it depends on what your
position is regarding improper use of the stream. If the policy is to protect
against that kind of mistake or to let it happen so that in the end the user
has to fix it's application.
> Jackrabbit does not allow concurrent reads to the data store if
> copyWhenReading=false
> -------------------------------------------------------------------------------------
>
> Key: JCR-1388
> URL: https://issues.apache.org/jira/browse/JCR-1388
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Affects Versions: 1.4
> Environment: WinXP x64, Eclipse, remote SQL Server 2005
> Reporter: Esteban Franqueiro
> Attachments: JCR-1388-datastore-concurrent-reads.2.patch,
> JCR-1388-datastore-concurrent-reads.4.patch,
> JCR-1388-datastore-concurrent-reads.patch, TestTwoGetStreams.java
>
>
> Jackrabbit does not allow concurrent reads to the data store if
> copyWhenReading=false, even if maxConnections>1.
> See JCR-1184 for a test for this problem (run it with copyWhenReading=false).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
