-
Type:
Suggestion
-
Resolution: Fixed
-
Component/s: Enterprise
-
None
JMX clients like jconsole use the JMX server port (which is random by default and not 3333) to communicate with bitbucket server. This makes it difficult to open the right firewall port on the server to permit JMX access. See, e.g., http://stackoverflow.com/questions/20884353/why-java-opens-3-ports-when-jmx-is-configured/21552812#21552812.
A simple fix can be made in bin/setenv.sh. That file currently adds "-Dcom.sun.management.jmxremote.port=${JMX_REMOTE_PORT}" to JMX_OPTS (in two places). It could add "-Dcom.sun.management.jmxremote.rmi.port=${JMX_REMOTE_PORT}" as well.
- is duplicated by
-
BSERV-9816 Allow com.sun.management.jmxremote.rmi.port to be set in set-jmx-opts.sh
- Closed