My Oracle Support Banner

WebLogic Server Show T3 Connections Although Corresponding Clients Don’t Exist Anymore (Doc ID 2731163.1)

Last updated on DECEMBER 16, 2023

Applies to:

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


WebLogic admin console shows t3 connections although corresponding clients don’t exist anymore

WebLogic Server 8. Clients connect to a WebLogic cluster via t3 cluster URL: t3://server1:port1,server2:port2,server3:port,server4:port4,server5:port5.
All client computers (Terminal Servers) where t3-clients are sitting are rebooted on daily basis. Hence, all server-side connections should be cleaned up by WebLogic.
However, it has been observed that connections are still seen in the WebLogic console until the Weblogic servers reboot occurs!

Stale/orphan T3 connections count can be seen from WLS console > servers > monitoring >Channels > click on Default[t3://HOSTNAME:PORT]

This has been observed even after rebooting the client machines.

At OS level, on checking with netstat grep $LISTEN_PORT on the servers, can see all connections to WebLogic have status ESTAB (established) even those of clients that don’t exist anymore. 

Implication: number of server-side t3 connections (sockets) managed by WebLogic are growing overtime beyond the configured socket count can cause the server unresponsive.



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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.