Statement Execution Is Stuck At "executeLargeBatch"
(Doc ID 3056365.1)
Last updated on NOVEMBER 08, 2024
Applies to:
JDBC - Version 10.1.0.2 and laterInformation in this document applies to any platform.
Symptoms
AFCS application uses Oracle 19.13 JDBC driver version to connect to ADBS-24.9.2.2
It also uses Hikari and other Apache libraries with batch size of 1000.
It was determined that after exactly 15 minutes, there is an IO Error: Connection timed out,
preceded by an exception for ClosedConnection.
The client side thread dump indicates that it is waiting for a server response, but the
database sessions are inactive and stay for more than 15 minutes, according to ADB team
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.SocketDispatcher.read0(java.base@17.0.8/Native Method)
at sun.nio.ch.SocketDispatcher.read(java.base@17.0.8/SocketDispatcher.java:47)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(java.base@17.0.8/IOUtil.java:330)
at sun.nio.ch.IOUtil.read(java.base@17.0.8/IOUtil.java:296)
at sun.nio.ch.IOUtil.read(java.base@17.0.8/IOUtil.java:259)
at sun.nio.ch.SocketChannelImpl.read(java.base@17.0.8/SocketChannelImpl.java:417)
at oracle.net.nt.TimeoutSocketChannel.read(TimeoutSocketChannel.java:174)
at oracle.net.nt.SSLSocketChannel.readFromSocket(SSLSocketChannel.java:602)
at oracle.net.nt.SSLSocketChannel.fillReadBuffer(SSLSocketChannel.java:330)
at oracle.net.nt.SSLSocketChannel.fillAndUnwrap(SSLSocketChannel.java:260)
Enabling the DCD did not help
Workaround:-
With smaller Batch size no issues observed.
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 |