BSDataSource": IO Error: Socket read timed - R12.2.5

[satish]

Hi Erman,

Need your help.

Apps Version R12.2.5 2 node shared appltop
2 node DB 19.17 version

Today we faced an issue with login and concurrent managers. We observed below errors in oacores. Any idea what could be wrong. On friday, we have changed the SGA and PGA parameters and enabled huge pages. This is the only change.

Till yesterday,it is working fine.  During the issue, we tried to connect as apps user from server. Sometimes,it connect quickly and sometimes it takes around 15 seconds to connect to database.


####<15 May, 2024 12:31:00 PM IST> <Warning> <JDBC> <erpprodapp01.ttd.com> <oacore_server1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <00667Y5dRGP4ioGqywaeMG0006Se0003PL> <1715756460022> <BEA-001129> <Received exception while creating connection for pool "EBSDataSource": IO Error: Socket read timed out.>

####<15 May, 2024 12:31:00 PM IST> <Info> <JDBC> <erpprodapp01.ttd.com> <oacore_server1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <00667Y5dRGP4ioGqywaeMG0006Se0003PL> <1715756460022> <BEA-001156> <Stack trace associated with message 001129 follows:

java.sql.SQLRecoverableException: IO Error: Socket read timed out

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:490)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:678)

at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:235)

at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:34)

at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:567)

at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:359)

at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:241)

at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1334)

at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1251)

at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:475)

at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:358)

at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:345)

at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:469)

at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:363)

at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:125)

at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:469)

at weblogic.jdbc.common.internal.RmiDataSource.getConnectionInternal(RmiDataSource.java:553)

at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:513)

at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at oracle.apps.fnd.security.DBConnObjWLSDSPool.getConnection(DBConnObjWLSDSPool.java:373)

at oracle.apps.fnd.security.AppsConnectionManagerWLSDS.dbConnect(AppsConnectionManagerWLSDS.java:223)

at oracle.apps.fnd.security.AppsConnectionManagerWLSDS.localAppsConnect(AppsConnectionManagerWLSDS.java:193)

at oracle.apps.fnd.security.AppsConnectionManagerWLSDS.makeGuestConnection(AppsConnectionManagerWLSDS.java:68)

at oracle.apps.fnd.security.DBConnObj.getLabelledConnection(DBConnObj.java:314)

at oracle.apps.fnd.security.DBConnObj.<init>(DBConnObj.java:233)

at oracle.apps.fnd.security.DBConnObjDS.<init>(DBConnObjDS.java:98)

at sun.reflect.GeneratedConstructorAccessor166.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:526)

at oracle.apps.fnd.common.Pool.createObject(Pool.java:1276)

Thanks,
SG

[ErmanArslansOracleBlog]

Check the database & Weblogic connection pool.. The problem is related with the database connection.. Possible reasons :

weblogic connection max capacity may be reached.
db - listener level issues.