Last updated on NOVEMBER 05, 2016
Applies to:Oracle Weblogic Server - Version 9.2 and later
Information in this document applies to any platform.
When a WebLogic Scripting Tool (WLST) script establishes a connection to a WebLogic Server instance, the underlying T3 connection does not get destroyed by the disconnect() command until the client JVM exits although the RMI connection that WLST establishes with the JMX Server is closed upon disconnect(). When WLST connects to a large number of different Administration Servers (for example 45) the WLST script suffers a performance degradation. This is due to a scarcity of socket readers (the default is 18). One workaround is to call the WLST script separately for each operation requiring a connection to an Administration Server, but in some production environments this is not practical. What other way is there to overcome this limitation?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms