-
Type: New Feature
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: QualifiedToSchedule
-
Component/s: nuxeoctl start/stop/admin
From http://answers.nuxeo.com/questions/3463/nuxeo-remote-jmx-monitoring-on-linux
While attempting to configure remote JMX monitoring with the Linux Tomcat distribution, I encountered a need to set the "java.rmi.server.hostname" property to the server's external/public DNS name as follows:
-Djava.rmi.server.hostname=your.public.dns
Since it is a common occurrence on Linux to have an internal DNS name that's different from the external/public DNS name, would it make sense to modify the bin/nuxeoctl script to calculate the server's external/public DNS name and set this property automatically? The HOST_FQDN could be calculated with code such as:
HOST_FQDN=$(hostname -f) HOST_DNS=$(host $HOST_FQDN | grep "has address") if [ $? -eq 0 ]; then # Use host from DNS HOST_FQDN=$(echo $HOST_DNS | awk '{ print $1 }') fi
Would it make sense to calculate and set the java.rmi.server.hostname property in nuxeoctl?
I think it could be useful for many other reasons (for instance, when the nuxeo.url property is not set).
- depends on
-
NXDOC-155 Expand Monitoring documentation to address using JMX with the default Tomcat distribution
- Open