[
https://issues.apache.org/jira/browse/OPENJPA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668911#action_12668911
]
Michael Dick commented on OPENJPA-881:
--------------------------------------
Hi Milosz,
I remember the conversation. All I really wanted to do in this issue is set
MaxIdle >=0 so that we maintain at least one connection. Along the way I split
out the settings we've used in the past into their own properties.
I've never messed around with the eviction times but they're easy enough to
specify via dbcp.args or I can split them into their own properties too if
you'd prefer that.
> 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.
