1##################################################################### 2# Default Configuration File for Java Platform Management 3##################################################################### 4# 5# The Management Configuration file (in java.util.Properties format) 6# will be read if one of the following system properties is set: 7# -Dcom.sun.management.jmxremote.port=<port-number> 8# or -Dcom.sun.management.snmp.port=<port-number> 9# or -Dcom.sun.management.config.file=<this-file> 10# 11# The default Management Configuration file is: 12# 13# $JRE/conf/management/management.properties 14# 15# Another location for the Management Configuration File can be specified 16# by the following property on the Java command line: 17# 18# -Dcom.sun.management.config.file=<this-file> 19# 20# If -Dcom.sun.management.config.file=<this-file> is set, the port 21# number for the management agent can be specified in the config file 22# using the following lines: 23# 24# ################ Management Agent Port ######################### 25# 26# For setting the JMX RMI agent port use the following line 27com.sun.management.jmxremote.port=${getFreePort} 28# 29# For setting the SNMP agent port use the following line 30# com.sun.management.snmp.port=<port-number> 31 32##################################################################### 33# Optional Instrumentation 34##################################################################### 35# 36# By default only the basic instrumentation with low overhead is on. 37# The following properties allow to selectively turn on optional 38# instrumentation which are off by default and may have some 39# additional overhead. 40# 41# com.sun.management.enableThreadContentionMonitoring 42# 43# This option enables thread contention monitoring if the 44# Java virtual machine supports such instrumentation. 45# Refer to the specification for the java.lang.management.ThreadMBean 46# interface - see isThreadContentionMonitoringSupported() method. 47# 48 49# To enable thread contention monitoring, uncomment the following line 50# com.sun.management.enableThreadContentionMonitoring 51 52##################################################################### 53# SNMP Management Properties 54##################################################################### 55# 56# If the system property -Dcom.sun.management.snmp.port=<port-number> 57# is set then 58# - The SNMP agent (with the Java virtual machine MIB) is started 59# that listens on the specified port for incoming SNMP requests. 60# - the following properties for read for SNMP management. 61# 62# The configuration can be specified only at startup time. 63# Later changes to the above system property (e.g. via setProperty method), this 64# config file, or the ACL file has no effect to the running SNMP agent. 65# 66 67# 68# ##################### SNMP Trap Port ######################### 69# 70# com.sun.management.snmp.trap=<trap-destination-port-number> 71# Specifies the remote port number at which managers are expected 72# to listen for trap. For each host defined in the ACL file, 73# the SNMP agent will send traps at <host>:<trap-destination-port-number> 74# Default for this property is 162. 75# 76 77# To set port for sending traps to a different port use following line 78# com.sun.management.snmp.trap=<trap-destination-port-number> 79 80# 81# ################ SNMP listen interface ######################### 82# 83# com.sun.management.snmp.interface=<InetAddress> 84# Specifies the local interface on which the SNMP agent will bind. 85# This is usefull when running on machines which have several 86# interfaces defined. It makes it possible to listen to a specific 87# subnet accessible through that interface. 88# Default for this property is "localhost". 89# 90# The format of the value for that property is any string accepted 91# by java.net.InetAddress.getByName(String). 92# 93 94# For restricting the port on which SNMP agent listens use following line 95# com.sun.management.snmp.interface=<InetAddress> 96 97# 98# #################### SNMP ACL file ######################### 99# 100# com.sun.management.snmp.acl=true|false 101# Default for this property is true. (Case for true/false ignored) 102# If this property is specified as false then the ACL file 103# is not checked: all manager hosts are allowed all access. 104# 105 106# For SNMP without checking ACL file uncomment the following line 107# com.sun.management.snmp.acl=false 108 109# 110# com.sun.management.snmp.acl.file=filepath 111# Specifies location for ACL file 112# This is optional - default location is 113# $JRE/conf/management/snmp.acl 114# 115# If the property "com.sun.management.snmp.acl" is set to false, 116# then this property and the ACL file are ignored. 117# Otherwise the ACL file must exist and be in the valid format. 118# If the ACL file is empty or non existent then no access is allowed. 119# 120# The SNMP agent will read the ACL file at startup time. 121# Modification to the ACL file has no effect to any running SNMP 122# agents which read that ACL file at startup. 123# 124 125# For a non-default acl file location use following line 126# com.sun.management.snmp.acl.file=filepath 127 128##################################################################### 129# RMI Management Properties 130##################################################################### 131# 132# If system property -Dcom.sun.management.jmxremote.port=<port-number> 133# is set then 134# - A MBean server is started 135# - JRE Platform MBeans are registered in the MBean server 136# - RMI connector is published in a private readonly registry at 137# specified port using a well known name, "jmxrmi" 138# - the following properties are read for JMX remote management. 139# 140# The configuration can be specified only at startup time. 141# Later changes to above system property (e.g. via setProperty method), 142# this config file, the password file, or the access file have no effect to the 143# running MBean server, the connector, or the registry. 144# 145 146# 147# ###################### RMI SSL ############################# 148# 149# com.sun.management.jmxremote.ssl=true|false 150# Default for this property is true. (Case for true/false ignored) 151# If this property is specified as false then SSL is not used. 152# 153 154# For RMI monitoring without SSL use the following line 155# com.sun.management.jmxremote.ssl=false 156 157# com.sun.management.jmxremote.ssl.enabled.cipher.suites=<cipher-suites> 158# The value of this property is a string that is a comma-separated list 159# of SSL/TLS cipher suites to enable. This property can be specified in 160# conjunction with the previous property "com.sun.management.jmxremote.ssl" 161# in order to control which particular SSL/TLS cipher suites are enabled 162# for use by accepted connections. If this property is not specified then 163# the SSL/TLS RMI Server Socket Factory uses the SSL/TLS cipher suites that 164# are enabled by default. 165# 166 167# com.sun.management.jmxremote.ssl.enabled.protocols=<protocol-versions> 168# The value of this property is a string that is a comma-separated list 169# of SSL/TLS protocol versions to enable. This property can be specified in 170# conjunction with the previous property "com.sun.management.jmxremote.ssl" 171# in order to control which particular SSL/TLS protocol versions are 172# enabled for use by accepted connections. If this property is not 173# specified then the SSL/TLS RMI Server Socket Factory uses the SSL/TLS 174# protocol versions that are enabled by default. 175# 176 177# com.sun.management.jmxremote.ssl.need.client.auth=true|false 178# Default for this property is false. (Case for true/false ignored) 179# If this property is specified as true in conjunction with the previous 180# property "com.sun.management.jmxremote.ssl" then the SSL/TLS RMI Server 181# Socket Factory will require client authentication. 182# 183 184# For RMI monitoring with SSL client authentication use the following line 185# com.sun.management.jmxremote.ssl.need.client.auth=true 186 187# com.sun.management.jmxremote.registry.ssl=true|false 188# Default for this property is false. (Case for true/false ignored) 189# If this property is specified as true then the RMI registry used 190# to bind the RMIServer remote object is protected with SSL/TLS 191# RMI Socket Factories that can be configured with the properties: 192# com.sun.management.jmxremote.ssl.enabled.cipher.suites 193# com.sun.management.jmxremote.ssl.enabled.protocols 194# com.sun.management.jmxremote.ssl.need.client.auth 195# If the two properties below are true at the same time, i.e. 196# com.sun.management.jmxremote.ssl=true 197# com.sun.management.jmxremote.registry.ssl=true 198# then the RMIServer remote object and the RMI registry are 199# both exported with the same SSL/TLS RMI Socket Factories. 200# 201 202# For using an SSL/TLS protected RMI registry use the following line 203com.sun.management.jmxremote.registry.ssl=true 204 205# 206# ################ RMI User authentication ################ 207# 208# com.sun.management.jmxremote.authenticate=true|false 209# Default for this property is true. (Case for true/false ignored) 210# If this property is specified as false then no authentication is 211# performed and all users are allowed all access. 212# 213 214# For RMI monitoring without any checking use the following line 215com.sun.management.jmxremote.authenticate=false 216 217# 218# ################ RMI Login configuration ################### 219# 220# com.sun.management.jmxremote.login.config=<config-name> 221# Specifies the name of a JAAS login configuration entry to use when 222# authenticating users of RMI monitoring. 223# 224# Setting this property is optional - the default login configuration 225# specifies a file-based authentication that uses the password file. 226# 227# When using this property to override the default login configuration 228# then the named configuration entry must be in a file that gets loaded 229# by JAAS. In addition, the login module(s) specified in the configuration 230# should use the name and/or password callbacks to acquire the user's 231# credentials. See the NameCallback and PasswordCallback classes in the 232# javax.security.auth.callback package for more details. 233# 234# If the property "com.sun.management.jmxremote.authenticate" is set to 235# false, then this property and the password & access files are ignored. 236# 237 238# For a non-default login configuration use the following line 239# com.sun.management.jmxremote.login.config=<config-name> 240 241# 242# ################ RMI Password file location ################## 243# 244# com.sun.management.jmxremote.password.file=filepath 245# Specifies location for password file 246# This is optional - default location is 247# $JRE/conf/management/jmxremote.password 248# 249# If the property "com.sun.management.jmxremote.authenticate" is set to 250# false, then this property and the password & access files are ignored. 251# Otherwise the password file must exist and be in the valid format. 252# If the password file is empty or non-existent then no access is allowed. 253# 254 255# For a non-default password file location use the following line 256# com.sun.management.jmxremote.password.file=filepath 257 258# 259# ################ RMI Access file location ##################### 260# 261# com.sun.management.jmxremote.access.file=filepath 262# Specifies location for access file 263# This is optional - default location is 264# $JRE/conf/management/jmxremote.access 265# 266# If the property "com.sun.management.jmxremote.authenticate" is set to 267# false, then this property and the password & access files are ignored. 268# Otherwise, the access file must exist and be in the valid format. 269# If the access file is empty or non-existent then no access is allowed. 270# 271 272# For a non-default password file location use the following line 273# com.sun.management.jmxremote.access.file=filepath 274