jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1456) Database connection pooling
Date Fri, 27 Nov 2009 17:18:20 GMT

    [ https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783135#action_12783135
] 

Stefan Guggisberg commented on JCR-1456:
----------------------------------------

> Would you be fine with an option that made the connection pool contain just a single
persistent connection (which would essentially match current functionality), or would you
rather keep the current code as is and introduce the pool-enabled code in separate packages
(see my earlier comment from 30/May/09)? 

personally i'd prefer the latter.

> Database connection pooling
> ---------------------------
>
>                 Key: JCR-1456
>                 URL: https://issues.apache.org/jira/browse/JCR-1456
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Jukka Zitting
>             Fix For: 2.0.0
>
>         Attachments: 777490.patch, dbcp.patch, dbcp.patch, JCR-1456-performance-trunk-test-setup.patch,
JCR-1456-performance.txt, JCR-1456.patch, patch-1456-1.txt, patch-1456-2.txt, patch-1456-3.txt
>
>
> Jackrabbit should use database connection pools instead of a single connection per persistence
manager, cluster journal, or database data store.

-- 
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