[
https://issues.apache.org/jira/browse/OPENJPA-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reopened OPENJPA-2754:
------------------------------------
[~solomax] I think I just catched a glitch.
In commit d874cbf you removed the AutoDriverDataSource and the automatic dbcp2
detection.
{quote} * DBCPDriverDataSource and AutoDriverDataSource are removed{quote}
This has quite some impact. The postgresql tests do not work any more since
there are tests which spawn up 100 Threads and thus overloading the postgresql
docker. In that case we got a connection failed Exception.
The second implication is that standard users would slow down quite heavily as
a Connection is re-established every time an EntityManager gets created.
What was the reason to remove this logic?
I've re-added the logic and all is green again now.
> 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)
