My Oracle Support Banner

WebLogic Server fails at startup due to "InterruptedIOException: Socket read timed out" errors (Doc ID 2428934.1)

Last updated on JULY 25, 2019

Applies to:

JDBC - Version 12.2.0.0.0 and later
Oracle WebLogic Server - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

A new FMW 12.2.1.3 environment has been installed and the configurations of the previous FMW installation is being copied to this new environment. The datasource connections and tuning settings are identical to the ones previously used in other FMW environments.

It is noticed that some of the WebLogic Servers (WLS) do not start due to the following error message:

<Jul 26, 2018 10:57:14,388 AM CEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application "<NAME>" due to error weblogic.application.ModuleException: java.io.InterruptedIOException: Socket read timed out
weblogic.application.ModuleException: java.io.InterruptedIOException: Socket read timed out
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:408)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:192)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:187)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
...
Caused By: java.io.InterruptedIOException: Socket read timed out
at oracle.net.nt.TimeoutSocketChannel.handleInterrupt(TimeoutSocketChannel.java:308)
at oracle.net.nt.TimeoutSocketChannel.<init>(TimeoutSocketChannel.java:85)
at oracle.net.nt.TcpNTAdapter.connect(TcpNTAdapter.java:182)
at oracle.net.nt.ConnOption.connect(ConnOption.java:164)
at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:473)
...

Other WLS servers which started successfully hit different errors in Runtime, such as:

####<Jul 26, 2018 12:23:44,856 PM CEST> <Error> <oracle.osb.reporting.impl.jmsreportingprovider> <[ACTIVE] ExecuteThread: '62' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <BEA1-3E847B0CA99FBD331483> <3872b7f6-36ea-48a8-9175-4f4cefb1df0f-000b7f30> <1532168624856> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: <NAME>] > <OSB-473514> <An unexpected error occurred while receiving the message in ReportingMDB java.sql.SQLException: Cannot obtain XAConnection
java.sql.SQLException: Cannot obtain XAConnection
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1655)
at weblogic.jdbc.jta.DataSource.getConnectionInternal(DataSource.java:520)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:497)
at weblogic.jdbc.common.internal.RmiDataSource.getConnectionInternal(RmiDataSource.java:614)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:594)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:587)
at com.bea.wli.reporting.jmsprovider.utils.ReportingUtil.__getConnection(ReportingUtil.java:99)
at com.bea.wli.reporting.jmsprovider.utils.ReportingUtil.access$000(ReportingUtil.java:48)
at com.bea.wli.reporting.jmsprovider.utils.ReportingUtil$1.run(ReportingUtil.java:80)
at com.bea.wli.reporting.jmsprovider.utils.ReportingUtil$1.run(ReportingUtil.java:78)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:368)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:163)
at com.bea.wli.sb.util.security.SecurityUtils.executeAs(SecurityUtils.java:102)
at com.bea.wli.sb.security.SecurityModuleImpl.runAlsbPrivilegedAction(SecurityModuleImpl.java:349)
at com.bea.wli.reporting.jmsprovider.utils.ReportingUtil.getConnection(ReportingUtil.java:78)
at com.bea.wli.reporting.jmsprovider.runtime.MDBMessageReporting.<init>(MDBMessageReporting.java:72)
at com.bea.wli.reporting.jmsprovider.runtime.ReportingMDB.getOrCreateMDBSync(ReportingMDB.java:177)
at com.bea.wli.reporting.jmsprovider.runtime.ReportingMDB.__onMessage(ReportingMDB.java:127)
at com.bea.wli.reporting.jmsprovider.runtime.ReportingMDB.access$000(ReportingMDB.java:45)
at com.bea.wli.reporting.jmsprovider.runtime.ReportingMDB$1.run(ReportingMDB.java:100)
at com.bea.wli.reporting.jmsprovider.runtime.ReportingMDB$1.run(ReportingMDB.java:98)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
...

Caused By: java.sql.SQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: IO Error: The Network Adapter could not establish the connection
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1525)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:451)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:360)
at weblogic.jdbc.common.internal.HAConnectionPool.reserve(HAConnectionPool.java:351)
at weblogic.jdbc.common.internal.HAConnectionPool.reserve(HAConnectionPool.java:242)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:148)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:94)
...

 

Using a simple JDBC java code, it is possible to reproduce the read timeout error (outside of FMW/WebLogic).

When the debug level is enabled, every time the error occurs, the SPID can not be given (It is NULL):

Jul 27, 2018 4:45:49 PM oracle.jdbc.driver.T4CConnection logon
INFO: Connection.logon: oracle.jdbc.driver.T4CConnection@1d9212d8
Jul 27, 2018 4:45:49 PM oracle.jdbc.driver.T4CConnection logon
INFO: Operating System Process Identifier (SPID): null
Jul 27, 2018 4:45:49 PM oracle.jdbc.driver.T4CConnection logon
INFO: DRCP Enabled: false
16:45:49LOOP: 243
+++++++++++++++++++++++++++++++
java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:770)
at oracle.jdbc.driver.PhysicalConnection.connect(PhysicalConnection.java:698)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:687)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at JdbcOracleConnection.main(JdbcOracleConnection.java:21)
... 6 more
Caused by: java.io.IOException: Socket read timed out, socket connect lapse 11 ms. /<IP> <PORT> 3 1 true
at oracle.net.nt.TcpNTAdapter.connect(TcpNTAdapter.java:205)
at oracle.net.nt.ConnOption.connect(ConnOption.java:157)

 

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.