jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1050) Remove synchronization from JNDI data sources
Date Wed, 08 Aug 2007 06:40:59 GMT

     [ https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting updated JCR-1050:
-------------------------------

    Affects Version/s:     (was: 1.3)
                           (was: 1.2.2)
                           (was: 1.2.1)
                           (was: 1.2.3)
                           (was: 1.1.1)
                           (was: 1.1)
                           (was: 1.0)
                           (was: 0.9)
                           (was: 1.0.1)
                           (was: 1.3.1)
                           (was: 1.4)
                           (was: 2.0)

This issue has been raised a few times before, and I agree with Padraic here. The synchronization
issue hasn't been that pressing before since the SharedItemStateManager was using a workspace-global
lock in any case, but with recent work that is no longer the case, and I see the database
synchronization becoming a bottleneck.

Pointers to some related discussions:

http://www.nabble.com/Thoughts-on-database-persistence-tf1302987.html
http://www.nabble.com/question-reagrding-JNDI-datasource-tf1760903.html
http://www.nabble.com/DP-Persistence-manager-implementation-tf1045939.html
http://www.nabble.com/Results-of-a-JR-Oracle-test-that-we-conducted-tf3333104.html
http://www.nabble.com/DbFileSystem-and-SimpleDbPersistenceManager---Connection-and-PreparedStatement-tf1474979.html


> Remove synchronization from JNDI data sources
> ---------------------------------------------
>
>                 Key: JCR-1050
>                 URL: https://issues.apache.org/jira/browse/JCR-1050
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: core
>            Reporter: Padraic Hannon
>         Attachments: JNDI_Datasource_Changes.diff
>
>
> Using datasources one should be able to rely on the application server to manage PreparedStatement
caches therefore pre-creating and holding onto the connection for long periods of time should
not be needed. This relates to improvement JCR-313, however, that change did not address the
benefits one could see in using an application server controlled datasource. Even if jackrabbit
does aim to use an embedded database such a system could be configured to use datasources
and could benefit from the removal of the synchronization. 

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


Mime
View raw message