bug #8171
javax.sql.DataSource.getConnection() implementation in WrappedCdmDataSource fails to cache the connection which and leaves it unclosed
100%
Description
When the existing cached connection in the WrappedCdmDataSource is null a new connection will be created but is not stored in the connection field. When closeOpenConnections() is being called the created connection is not closed
This issue is strongly related to #8170 but needs to be handled much earlier in order to void connections which are not closed after being used. See #8132 for symptoms.
the same account for getConnection(String username, String password)
It would be better to fix #8170, but this might require more time.
Question: Why closeOpenConnections(). The WrappedCdmDataSource always only handles only one connection and should actually not deal with more than one connection at the same time.
Related issues
Associated revisions
fix #8171 internally caching new connection in WrappedCdmDataSource to avoid connection leaks
fix #8171 internally caching new connection in WrappedCdmDataSource to avoid connection leaks
History
#1 Updated by Andreas Kohlbecker almost 2 years ago
- Description updated (diff)
#2 Updated by Andreas Kohlbecker almost 2 years ago
- Description updated (diff)
#3 Updated by Andreas Kohlbecker almost 2 years ago
- Related to bug #8132: phycobank cdm-server instance problems with db connections added
#4 Updated by Andreas Kohlbecker almost 2 years ago
- Related to bug #8170: javax.sql.DataSource.getConnection() implementation in WrappedCdmDataSource does not conform to the interface added
#5 Updated by Andreas Kohlbecker almost 2 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 50
Applied in changeset cdmlib|ddaf22cfc36cad56b677c8fecd8eb3e83db5cefb.
#6 Updated by Andreas Kohlbecker almost 2 years ago
- Description updated (diff)
#7 Updated by Andreas Kohlbecker almost 2 years ago
- Status changed from Resolved to Closed
- % Done changed from 50 to 100
We can close this ticket as solved, since fixing this issue did not cause any side effect problems
