You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2009/02/27 16:19:12 UTC

[jira] Closed: (OPENJPA-881) Enable connection pooling for testcases.

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

Michael Dick closed OPENJPA-881.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.3.0
                   1.2.1
                   1.0.4

> Enable connection pooling for testcases. 
> -----------------------------------------
>
>                 Key: OPENJPA-881
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-881
>             Project: OpenJPA
>          Issue Type: Improvement
>    Affects Versions: 1.0.4, 1.1.1, 1.2.1, 1.3.0, 2.0.0
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>             Fix For: 1.0.4, 1.2.1, 1.3.0, 2.0.0
>
>
> Test configurations currently use dbcp with MaxIdle=0, effectively no connection pool. For Derby this doesn't have much of an effect but with other databases, like DB2, setting MaxIdle=2 can dramatically improve the time taken to run the tests. 

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