[
https://issues.apache.org/jira/browse/OPENJPA-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-1764:
----------------------------------
Attachment: OPENJPA-1764-20100927.diff
Code to introduce automatic usage of Commons DBCP for Java SE apps in a
non-managed and non-transaction setup, when Commons DBCP is on the class path.
The default behavior is -
openjpa.jdbc.DriverDataSource=auto
but users can force usage of DBCP or fail if it not available by setting -
openjpa.jdbc.DriverDataSource=dbcp
or force the old behavior of using the ConnectionDriverName as-is by setting -
openjpa.jdbc.DriverDataSource=simple
The openjpa.ConnectionProperties setting can be used to provide Commons DBCP
arguments, like -
MaxActive=10,MaxIdle=0,MinIdle=0,MaxWait=10000
but the DBCPDriverDataSource will use the following defaults if none are
provided -
MaxActive=10,MaxIdle=1,MinIdle=0
> Automatically enable connection pooling in unmanaged environments
> -----------------------------------------------------------------
>
> Key: OPENJPA-1764
> URL: https://issues.apache.org/jira/browse/OPENJPA-1764
> Project: OpenJPA
> Issue Type: Sub-task
> Components: jdbc, performance
> Affects Versions: 2.1.0
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.1.0
>
> Attachments: OPENJPA-1764-20100927.diff
>
>
> When commons-dbcp is present on the classpath and we are running in a JSE or
> unmanaged environment, we should automatically configure
> DriverClassName=org.apache.commons.dbcp.BasicDataSource and apply some DBCP
> args (this might be the tricky part, based on the different dbcp args we have
> to use today for different databases...)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
