My Oracle Support Banner

The Description of Tunneling Client Ping and Tunneling Client Timeout Aren't Correct (Doc ID 3037370.1)

Last updated on JULY 25, 2024

Applies to:

Oracle WebLogic Server - Version 14.1.1.0.0 to 14.1.1.0.0 [Release 14c]
Information in this document applies to any platform.

Symptoms

 WebLogic seems not to work as following. Current behavior seems different.

https://docs.oracle.com/en/middleware/standalone/weblogic-server/14.1.1.0/cnfgd/web_server.html#GUID-93CF3768-F0C9-4F21-9CB7-B5BBE5CEE8D4

Tunneling Client Ping
When an HTTP tunnel connection is set up, the client automatically sends a request to the server, so that the server may volunteer a response to the client. The client may also include instructions in a request, but this behavior happens regardless of whether the client application needs to communicate with the server. If the server does not respond (as part of the application code) to the client request within the number of seconds set in this attribute, it does so anyway. The client accepts the response and automatically sends another request immediately.

Tunneling Client Timeout
If the number of seconds set in this attribute have elapsed since the client last sent a request to the server (in response to a reply), then the server regards the client as dead, and terminates the HTTP tunnel connection. The server checks the elapsed time at the interval specified by this attribute, when it would otherwise respond to the client's request.

 

 

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
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.