jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Padraic Hannon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1050) Remove synchronization from JNDI data sources
Date Mon, 29 Oct 2007 20:32:50 GMT

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

Padraic Hannon commented on JCR-1050:

I'll spend to work on this this week, I've done some testing, however, I am starting to think
the problem is larger than just here, as I get the same performance with or without synchronization.
I am thinking I should just close this until we can refactor jackrabbit with the SPI project
which should give us more separation of concerns.

> Remove synchronization from JNDI data sources
> ---------------------------------------------
>                 Key: JCR-1050
>                 URL: https://issues.apache.org/jira/browse/JCR-1050
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Padraic Hannon
>         Attachments: DatasourcePersistenceManager.java, DerbyPooledPersistenceManager.java,
JCR-1050.patch, JNDI_Datasource_Changes.diff, OracleDatasourcePersistenceManager.java
> 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.

View raw message