There is quite a bit of common boilerplate code in jdbcapi.StatementPoolingTest related to getting a custom connection, or rather more than one logical connection from a single pooled (physical) connection.
This could be factored out to make the test methods shorter, and to make the test methods more focused on whatever they're testing.
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Issue & fix info||Patch Available [ 10102 ]|
|Fix Version/s||10.10.0.0 [ 12321550 ]|
|Resolution||Fixed [ 1 ]|
|Workflow||jira [ 12762338 ]||Default workflow, editable Closed status [ 12802403 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|18h 56m||1||Kristian Waagan||22/Feb/13 09:24|
|557d 23h 6m||1||Knut Anders Hatlen||03/Sep/14 08:31|