RJVM Timeout Parameters Do Not Take Effect During T3 Protocol Initialization Phase (Doc ID 2258704.1)

Last updated on AUGUST 10, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.6 to 12.2.1.1.0
Information in this document applies to any platform.

Symptoms

Values for RJVM timeout are not honored during initialization of the T3 protocol. A thread dump will show the following long running thread (around 4 min):

Java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.net.SocketInputStream.read(SocketInputStream.java:182)
at java.io.DataInputStream.readLine(DataInputStream.java:496)
at weblogic.rjvm.t3.MuxableSocketT3.connect(MuxableSocketT3.java:408)
at weblogic.rjvm.t3.ConnectionFactoryT3.createConnection(ConnectionFactoryT3.java:34)
at weblogic.rjvm.ConnectionManager.createConnection(ConnectionManager.java:1792)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1424)
- locked <0xa9e21ca0> (a weblogic.rjvm.ConnectionManagerServer)
- locked <0xa9e21ca0> (a weblogic.rjvm.ConnectionManagerServer)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:443)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:260)
- locked <0xf17c71c0> (a java.lang.String)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms