[
https://issues.apache.org/jira/browse/DBCP-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated DBCP-346:
-----------------------------
Affects Version/s: (was: 2.0)
1.2.2
1.3
1.4
Fix Version/s: 1.4.1
1.3.1
Thanks for the patch!
I am +1 for including this in 1.3.1, 1.4.1 onward. Will review further and
commit if there are no objections.
As a workaround until fix versions are released, you can either
1. override BasicDataSource.createConnectionPool() and set the desired lifo
there
2. Use PoolingDataSource instead, configuring the pool directly.
> DBCP cannot set GenericObjectPool.lifo
> --------------------------------------
>
> Key: DBCP-346
> URL: https://issues.apache.org/jira/browse/DBCP-346
> Project: Commons Dbcp
> Issue Type: Improvement
> Affects Versions: 1.2.2, 1.3, 1.4
> Environment: All.
> Reporter: Ken Tatsushita
> Fix For: 1.3.1, 1.4.1
>
> Attachments: lifo_patch.txt
>
>
> Hi experts!
> I want to change the order of return connection.
> change the GenericObjectPool.lifo setting false.(default is true).
> However GenericObjectPool.lifo cannot be changed.
> Because the setter method is not implement in DBCP
> IMHO DBCP have to implement setter method of GenericObjectPool.lifo
> I made the patch that can change GenericObjectPool.lifo.
> Best regards.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
