Random Ports When Configure JMX PORT on WebLogic Server (Doc ID 2910109.1)

Last updated on DECEMBER 02, 2024

Applies to:

Goal

When using the following arguments for the WebLogic Server to enable JMX port, noticed that 3 ports are opened.
-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=34116 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
netstat -nap | grep [PORT1]
tcp 0 0 0.0.0.0:34116 0.0.0.0:* LISTEN [PORT1]/[WLS-ManagedServer1]
tcp 0 0 0.0.0.0:36217 0.0.0.0:* LISTEN [PORT1]/[WLS-ManagedServer1]
tcp 0 0 0.0.0.0:37057 0.0.0.0:* LISTEN [PORT1]/[WLS-ManagedServer1]

So defined -Dcom.sun.management.jmxremote.rmi.port=XXXXXXX and -Dcom.sun.management.jmxremote.local.port=XXXXXX.
Now it appears only apply to the RMI PORT. The LOCAL port continues as random port.
-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=34116 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

netstat -nap | grep [PORT2]
tcp 0 0 0.0.0.0:34116 0.0.0.0:* LISTEN [PORT2]/[WLS-ManagedServer1]
tcp 0 0 0.0.0.0:39649 0.0.0.0:* LISTEN [PORT2]/[WLS-ManagedServer1]

How to specify or assign a dedicate JMX port rather using the random ports ?

Solution

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