My Oracle Support Banner

Connections from ojdbc8.jar are 2X Slower than those from ojdbc6.jar (Doc ID 2759669.1)

Last updated on MARCH 16, 2021

Applies to:

JDBC - Version 11.2.0.4.0 to 20.0.0.0.0 [Release 11.2 to 20c]
Information in this document applies to any platform.

Symptoms

It has been noticed that the connection to the database is two times slower when using ojdbc8.jar than when using ojdbc6.jar.

Jobs that were running fine with ojdbc6.jar and JDK 16 are now taking more than 1 min on the initial connection to the database with 12.2.0.1 ojdbc8.jar and JDK 1.8.
It appears to be taking about 90 seconds to do the initial connect.  As a result, the following error is received:

Caused by: java.io.IOException: Broken pipe, Authentication lapse 0 ms.
       at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:790)
       ... 15 more
Caused by: java.io.IOException: Broken pipe
       at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
       at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:59)
       at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:105)
       at sun.nio.ch.IOUtil.write(IOUtil.java:77)
       at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:485)
       at oracle.net.nt.TimeoutSocketChannel.write(TimeoutSocketChannel.java:215)
       at oracle.net.ns.NIOPacket.writeToSocketChannel(NIOPacket.java:211)
       at oracle.net.ns.NIONSDataChannel.writeDataToSocketChannel(NIONSDataChannel.java:181)
       at oracle.net.ns.NIONSDataChannel.writeDataToSocketChannel(NIONSDataChannel.java:132)
       at oracle.net.ano.CryptoNIONSDataChannel.writeDataToSocketChannel(Unknown Source)
       at oracle.jdbc.driver.T4CMAREngineNIO.prepareForReading(T4CMAREngineNIO.java:96)
       at oracle.jdbc.driver.T4CMAREngineNIO.unmarshalUB1(T4CMAREngineNIO.java:534)
       at oracle.jdbc.driver.T4C8TTIdty.receive(T4C8TTIdty.java:728)
       at oracle.jdbc.driver.T4C8TTIdty.doRPC(T4C8TTIdty.java:639)
       at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1544)
       at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:518)
       ... 15 more

Increasing the INBOUND_CONNECT_TIMEOUT_LISTENER=240 (default is 60 seconds) in the database prevents the error, but the main issue is that the connections are slow.


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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.