Forum Stats

  • 3,816,609 Users
  • 2,259,213 Discussions


Oracle JDBC Driver throwing "Got minus one from a read call"

User_6FWIQ Member Posts: 3 Green Ribbon

Hi there,

I'm using a Docker container with Oracle 19c version at my machine. I started the container with -p 1521:1521 argument as well. So, for check if is ok, I connected to database via DBeaver and executed some queries. Everything was ok.

However, when I tried to start a Wildfly with ojdbc8.jar JDBC Driver (21c, 19c, 18c, and 12.2 supports) downloaded from Oracle site I got the follow error at server log.

Server Log

Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call

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.driver.OracleDriver.connect(

at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(

... 86 more

Caused by: Got minus one from a read call







at Source)

at Source)

at Source)

at Source)

at Source)


at oracle.jdbc.driver.T4CConnection.connect(

at oracle.jdbc.driver.T4CConnection.logon(

... 91 more

I looked inside Docker container database log and I saw the follow error at same time

Database Log

Fatal NI connect error 12170, connecting to:



TNS for Linux: Version - Production

Oracle Bequeath NT Protocol Adapter for Linux: Version - Production

TCP/IP NT Protocol Adapter for Linux: Version - Production


 Time: 08-APR-2022 11:35:55

 Tracing not turned on.

 Tns error struct:

  ns main err code: 12535

 TNS-12535: TNS:operation timed out

  ns secondary err code: 12606

  nt main err code: 0

  nt secondary err code: 0

  nt OS err code: 0

Also, I started some networks checks like telnet 1521 and connection was ok. After that, I figured it was a kind of driver problem because DBeaver was connecting normally at same database.

So, I exchanged Wildfly JDBC driver by DBeaver driver. After that, Wildfly started without any error. My application did queries like expected.

I concluded that it is a driver issue because DBeaver had ojdbc8.jar that it was build to database version. The Wildfly jar that I downloaded from Oracle website that it was build to database version. I tested another one it was build to but I had the same problem.

Some one from Oracle could analyze these information to be sure if it is a driver issue?


After some researches at Google, I found a workaround that works for me without change the JDBC driver. Instead of using or localhost I setup my connection with hosted IP machine. It is works fine. However it is very bad need to do that.