[ https://issues.apache.org/jira/browse/OPENJPA-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731999#comment-16731999 ]
ASF subversion and git services commented on OPENJPA-2754: ---------------------------------------------------------- Commit d3790f70c7d8a0e7a85c1ad95730605c33c4d818 in openjpa's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=d3790f7 ] OPENJPA-2754 also move postgres config to dbcp2 maxTotal maxActive doesn't exist anymore. It is now maxTotal. > 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 > Assignee: Maxim Solodovnik > 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)