Draining of JDBC Connections During Planned Outage with Third-Party Liberty Connection Pool
(Doc ID 3020142.1)
Last updated on MAY 01, 2024
Applies to:
JDBC - Version 21.6 and laterInformation in this document applies to any platform.
Symptoms
An application using JDBC 21.6 driver (ojdbc8.jar) with Liberty 23.0.0.12 pooled connections did not mark connections as “stale" during a controlled Oracle database 19.20 failover (planned outage due to scheduled Linux OS update).
The sessions remained connected to the “failed” database node and did not move to the available one, causing the XA transactions to get lost for a specific datasource.
The connections were still in Liberty's connection pool, which is believed to be caused due to JDBC not marking the connection as "stale" as seen in the trace.log:
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |