0N/A#####################################################################
0N/A# Default Configuration File for Java Platform Management
0N/A#####################################################################
0N/A# will be read if one of the following system properties is set:
0N/A# The default Management Configuration file is:
0N/A# Another location for the Management Configuration File can be specified
0N/A# by the following property on the Java command line:
0N/A# number for the management agent can be specified in the config file
0N/A# using the following lines:
0N/A# ################ Management Agent Port #########################
0N/A# For setting the JMX RMI agent port use the following line
0N/A# For setting the SNMP agent port use the following line
0N/A#####################################################################
0N/A# Optional Instrumentation
0N/A#####################################################################
0N/A# By default only the basic instrumentation with low overhead is on.
0N/A# The following properties allow to selectively turn on optional
0N/A# instrumentation which are off by default and may have some
0N/A# additional overhead.
0N/A# This option enables thread contention monitoring if the
0N/A# Java virtual machine supports such instrumentation.
0N/A# interface - see isThreadContentionMonitoringSupported() method.
0N/A# To enable thread contention monitoring, uncomment the following line
0N/A#####################################################################
0N/A# SNMP Management Properties
0N/A#####################################################################
0N/A# - The SNMP agent (with the Java virtual machine MIB) is started
0N/A# that listens on the specified port for incoming SNMP requests.
0N/A# - the following properties for read for SNMP management.
0N/A# The configuration can be specified only at startup time.
0N/A# Later changes to the above system property (
e.g. via setProperty method), this
0N/A# config file, or the ACL file has no effect to the running SNMP agent.
0N/A# ##################### SNMP Trap Port #########################
# Specifies the remote port number at which managers are expected
# to listen for trap. For each host defined in the ACL file,
# the SNMP agent will send traps at <host>:<trap-destination-port-number>
# Default for this property is 162.
# To set port for sending traps to a different port use following line
# ################ SNMP listen interface #########################
# Specifies the local interface on which the SNMP agent will bind.
# This is usefull when running on machines which have several
# interfaces defined. It makes it possible to listen to a specific
# subnet accessible through that interface.
# Default for this property is "localhost".
# The format of the value for that property is any string accepted
# For restricting the port on which SNMP agent listens use following line
# #################### SNMP ACL file #########################
# Default for this property is true. (Case for
true/false ignored)
# If this property is specified as false then the ACL file
# is not checked: all manager hosts are allowed all access.
# For SNMP without checking ACL file uncomment the following line
# Specifies location for ACL file
# This is optional - default location is
# then this property and the ACL file are ignored.
# Otherwise the ACL file must exist and be in the valid format.
# If the ACL file is empty or non existent then no access is allowed.
# The SNMP agent will read the ACL file at startup time.
# Modification to the ACL file has no effect to any running SNMP
# agents which read that ACL file at startup.
# For a non-default acl file location use following line
#####################################################################
# RMI Management Properties
#####################################################################
# - A MBean server is started
# - JRE Platform MBeans are registered in the MBean server
# - RMI connector is published in a private readonly registry at
# specified port using a well known name, "jmxrmi"
# - the following properties are read for JMX remote management.
# The configuration can be specified only at startup time.
# Later changes to above system property (
e.g. via setProperty method),
# this config file, the password file, or the access file have no effect to the
# running MBean server, the connector, or the registry.
# ###################### RMI SSL #############################
# Default for this property is true. (Case for
true/false ignored)
# If this property is specified as false then SSL is not used.
# For RMI monitoring without SSL use the following line
# The value of this property is a string that is a comma-separated list
# of
SSL/TLS cipher suites to enable. This property can be specified in
# in order to control which particular
SSL/TLS cipher suites are enabled
# for use by accepted connections. If this property is not specified then
# the
SSL/TLS RMI Server Socket Factory uses the
SSL/TLS cipher suites that
# are enabled by default.
# The value of this property is a string that is a comma-separated list
# of
SSL/TLS protocol versions to enable. This property can be specified in
# in order to control which particular
SSL/TLS protocol versions are
# enabled for use by accepted connections. If this property is not
# specified then the
SSL/TLS RMI Server Socket Factory uses the
SSL/TLS# protocol versions that are enabled by default.
# Default for this property is false. (Case for
true/false ignored)
# If this property is specified as true in conjunction with the previous
# Socket Factory will require client authentication.
# For RMI monitoring with SSL client authentication use the following line
# Default for this property is false. (Case for
true/false ignored)
# If this property is specified as true then the RMI registry used
# to bind the RMIServer remote object is protected with
SSL/TLS# RMI Socket Factories that can be configured with the properties:
# If the two properties below are true at the same time,
i.e.# then the RMIServer remote object and the RMI registry are
# both exported with the same
SSL/TLS RMI Socket Factories.
# For using an
SSL/TLS protected RMI registry use the following line
# ################ RMI User authentication ################
# Default for this property is true. (Case for
true/false ignored)
# If this property is specified as false then no authentication is
# performed and all users are allowed all access.
# For RMI monitoring without any checking use the following line
# ################ RMI Login configuration ###################
# Specifies the name of a JAAS login configuration entry to use when
# authenticating users of RMI monitoring.
# Setting this property is optional - the default login configuration
# specifies a file-based authentication that uses the password file.
# When using this property to override the default login configuration
# then the named configuration entry must be in a file that gets loaded
# by JAAS. In addition, the login module(s) specified in the configuration
# should use the name
and/or password callbacks to acquire the user's
# credentials. See the NameCallback and PasswordCallback classes in the
# false, then this property and the password & access files are ignored.
# For a non-default login configuration use the following line
# ################ RMI Password file location ##################
# Specifies location for password file
# This is optional - default location is
# false, then this property and the password & access files are ignored.
# Otherwise the password file must exist and be in the valid format.
# If the password file is empty or non-existent then no access is allowed.
# For a non-default password file location use the following line
# ################ RMI Access file location #####################
# Specifies location for access file
# This is optional - default location is
# false, then this property and the password & access files are ignored.
# Otherwise, the access file must exist and be in the valid format.
# If the access file is empty or non-existent then no access is allowed.
# For a non-default password file location use the following line