Hi ,
i am seeing Login Timed out errors at random times everyday in server error logs. No issues with Database duirng that specific interval when issue occurred.

Version 8.2.2.0
Updates EstdCommonLib_7.1_Fix12
IS_8.2_SP2_Core_Fix6
TNS_8.2_SP2_Fix10
OS.Name Windows Server 2008 R2
connecting to SQL server

error:
[SoftwareAG][SQLServer JDBC Driver]Login has timed out.

error message:
stack trace:
java.sql.SQLException: [SoftwareAG][SQLServer JDBC Driver]Login has timed out.
at com.wm.dd.jdbc.sqlserverbase.ddb_.b(Unknown Source)
at com.wm.dd.jdbc.sqlserverbase.ddb_.a(Unknown Source)
at com.wm.dd.jdbc.sqlserverbase.ddb9.b(Unknown Source)
at com.wm.dd.jdbc.sqlserverbase.ddb9.a(Unknown Source)
at com.wm.dd.jdbc.sqlserverbase.ddaj.(Unknown Source)
at com.wm.dd.jdbc.sqlserverbase.BaseConnection$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at com.wm.dd.jdbc.sqlserverbase.BaseConnection.a(Unknown Source)
at com.wm.dd.jdbc.sqlserverbase.BaseConnection.a(Unknown Source)
at com.wm.dd.jdbc.sqlserverbase.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:185)
at com.wm.app.jdbc.JDBCConnection.(JDBCConnection.java:42)
at com.wm.app.jdbc.JDBCConnectionPool.getAvailConnection(JDBCConnectionPool.java:253)
at com.wm.app.jdbc.JDBCConnectionPool.getConnection(JDBCConnectionPool.java:143)
at com.wm.app.jdbc.JDBCConnectionPool.getConnection(JDBCConnectionPool.java:129)
at com.wm.app.b2b.server.scheduler.ScheduleDB.getConnection(ScheduleDB.java:840)
at com.wm.app.b2b.server.scheduler.ScheduleDB.runNextTask(ScheduleDB.java:1163)
at com.wm.app.b2b.server.scheduler.ScheduleManager.run(ScheduleManager.java:133)
at com.wm.util.pool.PooledThread.run(PooledThread.java:131)
at java.lang.Thread.run(Thread.java:662)

Can someone advise me how to get rid off these errors.

Thanks,
Mahesh

@Mahesh,

I assume you have taken care of the following:

1. Bounced your JDBC connection
2. Identified no network issue
3. Nothing changed at DB or IS level [Patches or Updates]

Are you getting transaction failures because of this issue?

HTH.

Thanks,
Rankesh

Thank you so much for the reply Kumar.
yes, there were couple of transactions failed and issue identified on the DB and resolved

Thanks,
Mahesh

Hi Mahesh,

We have share with me what was changed on the DB side? We have been running into this issue for the last couple of days.

Let me help you here…

1> wM version with IS core fix levels?

2> I assume this should not be a webMethods issue, can you please check with the DBA about these error… let them check their logs duirng you see these errors on IS

3> This can also be due to the network block or network issue. Also check with network team.

4> Can you share the screen of your JDBC pools with the configuration details.

Yes, I agree. Involve networking team along with DBA team to identify and fixing the issue.

Thanks,