[
https://issues.apache.org/jira/browse/OPENJPA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668836#action_12668836
]
Milosz Tylenda commented on OPENJPA-881:
----------------------------------------
Mike, we have once discussed it here [1], maybe it's worth re-reading. I run
the test suite on various databases and found the below settings quite useful
on my system (all databases and OpenJPA are co-located):
<dbcp.args>MaxActive=100,MaxIdle=10,MaxWait=10000,timeBetweenEvictionRunsMillis=2000,minEvictableIdleTimeMillis=1000</dbcp.args>
[1] http://n2.nabble.com/Test-suite-slow-on-DB2-td1115993.html#a1115993
> 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
>
> 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.
