[jira] Resolved: (JCR-1825) DBDataStore doesn't support concurrent reads

2008-10-28 Thread Thomas Mueller (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-1825. - Resolution: Fixed Committed in revision 708598. > DBDataStore doesn't support concurre

[jira] Commented: (JCR-1825) DBDataStore doesn't support concurrent reads

2008-10-28 Thread Jukka Zitting (JIRA)
ound (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

[jira] Updated: (JCR-1825) DBDataStore doesn't support concurrent reads

2008-10-21 Thread Thomas Mueller (JIRA)
ould be renamed to 'DbResource', I will do that later. > DBDataStore doesn't support concurrent reads > > > Key: JCR-1825 > URL: https://issues.apache.org/jira/browse/JCR-1825 >

[jira] Commented: (JCR-1825) DBDataStore doesn't support concurrent reads

2008-10-21 Thread JIRA
from the DatabaseHelper instead of ConnectionRecoveryManager so we can delete the Method in the ConnectionRecoveryManager > DBDataStore doesn't support concurrent reads > > > Key: JCR-1825 > URL: https:

[jira] Commented: (JCR-1825) DBDataStore doesn't support concurrent reads

2008-10-21 Thread Przemo Pakulski (JIRA)
low changes in DbInputStream class, but I assume they are not so important. > DBDataStore doesn't support concurrent reads > > > Key: JCR-1825 > URL: https://issues.apache.org/jira/browse/JCR-1825

[jira] Issue Comment Edited: (JCR-1825) DBDataStore doesn't support concurrent reads

2008-10-21 Thread Przemo Pakulski (JIRA)
= moveToTempFile(result); result = new TempFileInputStream(temp); + DatabaseHelper.closeSilently(rs); + putBack(conn); dbResources = new DbResources(result); } I do not follow changes in DbInputStream class, but I assume they are not so important. > DBDataStore doesn

[jira] Updated: (JCR-1825) DBDataStore doesn't support concurrent reads

2008-10-21 Thread Thomas Mueller (JIRA)
thers can have a look at it. > DBDataStore doesn't support concurrent reads > > > Key: JCR-1825 > URL: https://issues.apache.org/jira/browse/JCR-1825 > Project: Jackrabbi

[jira] Commented: (JCR-1825) DBDataStore doesn't support concurrent reads

2008-10-21 Thread Thomas Mueller (JIRA)
ks for finding this problem! Regards, Thomas > DBDataStore doesn't support concurrent reads > > > Key: JCR-1825 > URL: https://issues.apache.org/jira/browse/JCR-1825 > Proj

[jira] Commented: (JCR-1825) DBDataStore doesn't support concurrent reads

2008-10-21 Thread Przemo Pakulski (JIRA)
null) { DatabaseHelper.closeSilently(rs); try { store.putBack(conn); } catch (Exception e) { log.info("Closing DbResources: ", e); } } } } Is it ok ? > DBDataStore doesn't su

[jira] Commented: (JCR-1825) DBDataStore doesn't support concurrent reads

2008-10-21 Thread Przemo Pakulski (JIRA)
sage of DBDataStore is dangerous, could be a bottleneck depending how long streams are kept open. If streams are not closed DBDataStore hangs/locks. > DBDataStore doesn't support concurrent reads > > > Key: JCR-1825

[jira] Created: (JCR-1825) DBDataStore doesn't support concurrent reads

2008-10-21 Thread Przemo Pakulski (JIRA)
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

Re: DbDataStore doesn't support concurrent reads

2008-02-14 Thread Jukka Zitting
Hi, On Wed, Feb 13, 2008 at 4:40 PM, Esteban Franqueiro <[EMAIL PROTECTED]> wrote: > As the subject says, the DbDataStore doesn't support concurrent reads if > copyWhenReading is set to > false (the javadoc says so). This is a major problem for users (like me) >

DbDataStore doesn't support concurrent reads

2008-02-13 Thread Esteban Franqueiro
Hi all. As the subject says, the DbDataStore doesn't support concurrent reads if copyWhenReading is set to false (the javadoc says so). This is a major problem for users (like me) that have the complete repository on a database server. There's an easy fix for this, and that is to ass