[
https://issues.apache.org/jira/browse/OPENJPA-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16666381#comment-16666381
]
ASF subversion and git services commented on OPENJPA-2754:
----------------------------------------------------------
Commit 5c38bfaa49a2f9485a690e147f07399047f7d2d2 in openjpa's branch
refs/heads/master from [~struberg]
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=5c38bfa ]
OPENJPA-2754 update to latest dbcp2 SNAPSHOT
This also requires us to update to apache commons-pool-2.6.1-SNAPSHOT
and commons-dbcp2-2.6.0-SNAPSHOT.
Both are NOT yet released, but important to solve a deadlock which kills
our unit tests and has already hit me in production as well.
> update to latest dbcp and verify moving from maxActive to maxTotal
> ------------------------------------------------------------------
>
> Key: OPENJPA-2754
> URL: https://issues.apache.org/jira/browse/OPENJPA-2754
> Project: OpenJPA
> Issue Type: Task
> Components: jdbc
> Affects Versions: 3.0.0
> Reporter: Mark Struberg
> Priority: Major
> Fix For: 3.0.1
>
>
> commons-dbcp 2 moved from maxActive to maxTotal
> https://commons.apache.org/proper/commons-dbcp/
> https://commons.apache.org/proper/commons-dbcp/configuration.html
> But all across our build we still use MaxActive.
> Do we like to keep this? Do we (via reflection) don't care and users need to
> care for themselves if they switch?
> Do we do it right in our unit tests right now?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
