[SoftwareAG][Oracle JDBC Driver]Login has timed out.; Error Code: 0; SQLState: HYT00

[Niranth_NS]

Product component IS: IS version 9.12, IS fix level IS_9.12_Core_Fix17, OS Red Hat Enterprise Linux Server 7.7

We are updating the JDBC Connection Pool Alias to the new Oracle Schema with all the tables already created and Test connection is failing with error “[SoftwareAG][Oracle JDBC Driver]Login has timed out.; Error Code: 0; SQLState: HYT00”

We have a network open already from IS server machine to Oracle DB machine.

What are the other possible cause? Please advise.

java.sql.SQLException: [SoftwareAG][Oracle JDBC Driver]Login has timed out.
at com.wm.dd.jdbc.oraclebase.ddcr.b(Unknown Source)
at com.wm.dd.jdbc.oraclebase.ddcr.a(Unknown Source)
at com.wm.dd.jdbc.oraclebase.ddcq.b(Unknown Source)
at com.wm.dd.jdbc.oraclebase.ddcq.a(Unknown Source)
at com.wm.dd.jdbc.oraclebase.ddak.a(Unknown Source)
at com.wm.dd.jdbc.oraclebase.BaseConnection$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at com.wm.dd.jdbc.oraclebase.BaseConnection.b(Unknown Source)
at com.wm.dd.jdbc.oraclebase.BaseConnection.a(Unknown Source)
at com.wm.dd.jdbc.oraclebase.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at com.wm.app.jdbc.JDBCConnection.(JDBCConnection.java:51)
at com.wm.app.jdbc.JDBCConnectionPool.getAvailConnection(JDBCConnectionPool.java:473)
at com.wm.app.jdbc.JDBCConnectionPool.getAvailOpenConnection(JDBCConnectionPool.java:419)
at com.wm.app.jdbc.JDBCConnectionPool.getConnection(JDBCConnectionPool.java:229)
at com.wm.app.jdbc.JDBCConnectionPool.getConnection(JDBCConnectionPool.java:209)
at com.wm.app.b2b.server.scheduler.ScheduleDB.getConnection(ScheduleDB.java:437)
at com.wm.app.b2b.server.scheduler.Transaction.(Transaction.java:47)
at com.wm.app.b2b.server.scheduler.QueryTransaction.(QueryTransaction.java:12)
at com.wm.app.b2b.server.scheduler.Util.getComponentLevel(Util.java:145)
at com.wm.app.b2b.server.scheduler.TimeMigrator.checkDBLevel(TimeMigrator.java:97)
at com.wm.app.b2b.server.scheduler.ScheduleDB.init(ScheduleDB.java:372)
at com.wm.app.b2b.server.scheduler.ScheduleManager.run(ScheduleManager.java:168)
at com.wm.util.pool.PooledThread.run(PooledThread.java:127)
at java.lang.Thread.run(Thread.java:748)

Regards,
Niranth

[Venkata_Kasi_Viswanath_Mugada1 (Kasi Mugada)]

Possible reasons are -

1. Connectivity not established from the IS to the DB server
2. DB or Listener is not online or not accepting connections
3. Insufficient request timeout setting (less likely) on either side

You’ll have to work with the DBA.

KM

[Niranth_NS]

Hi Kasi,

Thanks for the response.

Already found the issue is in network by increasing the login timeout value, we going to DB to login is slowwww and timed out.

So we requested DBA/Infra team to check on the slowness as increasing the login time out is not a solution.

Regards,
Niranth