In WebLogic Server, WLST Does Not Close Network Connection Following Disconnect Command
(Doc ID 1585512.1)
Last updated on AUGUST 12, 2021
Applies to:
Oracle WebLogic Server - Version 10.0 and laterInformation in this document applies to any platform.
Symptoms
In WebLogic Server. run the WLST connect() command and successfully connect to a running WebLogic server. Run the disconnect() command, and message indicates successful disconnection. However, the underlying network connection is not closed, and remains established (connected) until exit from WLST. Linux tools such as lsof and netstat show the open network connection. Java stack (jstack command) shows a thread for the Socket connection. If WLST is connected to a different WebLogic server URL and then disconnected, the number of open connections and number of Socket handling threads increases.
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 |