Application Continuity Throws Exception No more data to read from socket For Commits After Failover
(Doc ID 2197029.1)
Last updated on AUGUST 29, 2023
Applies to:
JDBC - Version 12.1.0.2.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.1.0.2 version, JDBC
While testing Application Continuity for 12c database with JDBC 12.1.0.2, failover works successfully if entire committed transaction is failed over to surviving node, but it fails if executing commit after failover to survival node like below:
Error ---
Exception in thread "main" java.sql.SQLRecoverableException: IO Error: Connection reset
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:752)
at oracle.jdbc.driver.PhysicalConnection.connect(PhysicalConnection.java:662)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:560)
at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:311)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:235)
at oracle.jdbc.replay.OracleDataSourceImpl.getConnectionInternal(OracleDataSourceImpl.java:370)
at oracle.jdbc.replay.OracleDataSourceImpl.getConnection(OracleDataSourceImpl.java:283)
at oracle.jdbc.replay.OracleDataSourceImpl.getConnection(OracleDataSourceImpl.java:266)
at AcTest.main(AcTest.java:14)
Caused by: java.net.SocketException: Connection reset
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Configure Application Continuity
2. Run application. Before transaction is committed, bring down node 1.
Changes
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 |
Changes |
Cause |
Solution |
References |