[
https://issues.apache.org/jira/browse/DBCP-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved DBCP-61.
-----------------------------
Resolution: Duplicate
Having looked at DBCP-8 and this issue, they are trying to solve the same
problem. Given we only need one solution I am going to go with the approach in
DBCP-8. My main reason for doing this is simplicity. There appears to be far
fewer edge cases and things that could go wrong in the approach outlined in
DBCP-8.
If the DBCP-8 approach fails for some unforeseen reason then I'll re-open this
issue and look again at the approach described here.
> [dbcp] Individual connection close method
> -----------------------------------------
>
> Key: DBCP-61
> URL: https://issues.apache.org/jira/browse/DBCP-61
> Project: Commons Dbcp
> Issue Type: Bug
> Environment: Operating System: Windows XP
> Platform: PC
> Reporter: Srinath Narasimhan
> Assignee: Phil Steitz
> Fix For: 1.3
>
>
> The PerUserPoolDataSource object has a close method which closes all the
> connection that is being maintained by the pool. I have a need where the
> users
> can change their passwords, which requires closing the existing connection
> and
> opening a new one. I have a close method which takes a user as a parameter
> which will close all the connections for the specified user name.
> I have pasted the code here.
> /**
> * Close pool for particular user
> *
> */
> public void close(String user) {
> try {
> PoolKey key = getPoolKey(user);
> ObjectPool pool = (ObjectPool) pools.get(key);
> pool.close();
> } catch (Exception closePoolException) {
> closePoolException.printStackTrace();
> }
> }
> My questions are are is this is a right way to approach or should there a
> change password method which should do that ? If the above code can be added
> to the main stream ( if it is good, it will be great).
> Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
