Application Continuity Throws Exception No more data to read from socket For Commits After Failover

(Doc ID 2197029.1)

Last updated on FEBRUARY 07, 2018

Applies to:

JDBC - Version and later
Information in this document applies to any platform.


On : version, JDBC

While testing Application Continuity for 12c database with JDBC, 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(
  at oracle.jdbc.driver.PhysicalConnection.connect(
  at oracle.jdbc.driver.T4CDriverExtension.getConnection(
  at oracle.jdbc.driver.OracleDriver.connect(
  at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(
  at oracle.jdbc.pool.OracleDataSource.getConnection(
  at oracle.jdbc.replay.OracleDataSourceImpl.getConnectionInternal(
  at oracle.jdbc.replay.OracleDataSourceImpl.getConnection(
  at oracle.jdbc.replay.OracleDataSourceImpl.getConnection(
  at AcTest.main(
Caused by: Connection reset

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.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms