Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update basic DataSource implementations to no longer use broken FBConnectionPoolDataSource [JDBC179] #226

Closed
firebird-automations opened this issue Jul 30, 2011 · 5 comments
Closed

Update basic DataSource implementations to no longer use broken FBConnectionPoolDataSource [JDBC179] #226

firebird-automations opened this issue Jul 30, 2011 · 5 comments
Assignees
@mrotteveel
Labels
component: connection pool fix-version: Jaybird 2.2 priority: major resolution: wontfix type: sub-task

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

Jira_subtask_inward JDBC176

Some of the DataSource implementation use the broken FBConnectionPoolDataSource implementation: change implementation so they no longer use this implementation:
Options:
1) Use new implementation of ConnectionPoolDataSource created in JDBC177
2) Use basic driver as connection source
3) Use FBXADataSource

Potentially affected classes:
* FBWrappingDataSource (either 1 or 2)
* AppServerXADataSource (only 3)
@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 2.2 [ 10053 ]

Component: Connection pool [ 10054 ]

description: Some of the DataSource implementation use the broken FBConnectionPoolDataSource implementation: change implementation so they no longer use this implementation:
Options:
1) Use new implementation of ConnectionPoolDataSource created in JDBC177
2) Use basic driver as connection source
3) Use FBXADataSource

Potentially affected classes:
* FBWrappingDataSource (either 1 or 2)
* AppServerXADataSource (only 3)

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

See also comment in JDBC177, FBWrappingDataSource is not affected by the bug, so can probably be left as is for 2.2.

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

Opted to leave other datasources as is for Jaybird 2.2

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mrotteveel mrotteveel

Labels
component: connection pool fix-version: Jaybird 2.2 priority: major resolution: wontfix type: sub-task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mrotteveel @firebird-automations