[
https://issues.apache.org/jira/browse/DBCP-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mladen Adamovic resolved DBCP-394.
----------------------------------
Resolution: Invalid
the reason for braking the code was not BasicDataSource problem but another
static caching which was app crossing. Sorry about the invalid report.
> BasicDataSource doesn't work correct when using two objects with different
> connection URLs
> ------------------------------------------------------------------------------------------
>
> Key: DBCP-394
> URL: https://issues.apache.org/jira/browse/DBCP-394
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 1.4
> Environment: N/A, but using Mysql and Linux
> Reporter: Mladen Adamovic
> Original Estimate: 84h
> Remaining Estimate: 84h
>
> It looks like that if I create one BasicDataSource for one DB and second
> BasicDataSource for another DB that they connections got messed up so the app
> brakes.
> I moved not to use BasicDataSource but plain connections and the problem
> looks like being resolved.
> I put this as a major issue since I don't find it documented and of course
> two objects shall be supported unless it's singleton. Also this could brake
> app in production which happened to me.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
