1
#####################################################################
2
# Default Configuration File for Java Platform Management
3
#####################################################################
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>
11
# The default Management Configuration file is:
13
# $JRE/lib/management/management.properties
15
# Another location for the Management Configuration File can be specified
16
# by the following property on the Java command line:
18
# -Dcom.sun.management.config.file=<this-file>
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:
24
# ################ Management Agent Port #########################
26
# For setting the JMX RMI agent port use the following line
27
# com.sun.management.jmxremote.port=<port-number>
28
com.sun.management.jmxremote.port=54322
30
# For setting the SNMP agent port use the following line
31
# com.sun.management.snmp.port=<port-number>
34
#####################################################################
35
# Optional Instrumentation
36
#####################################################################
38
# By default only the basic instrumentation with low overhead is on.
39
# The following properties allow to selectively turn on optional
40
# instrumentation which are off by default and may have some
41
# additional overhead.
43
# com.sun.management.enableThreadContentionMonitoring
45
# This option enables thread contention monitoring if the
46
# Java virtual machine supports such instrumentation.
47
# Refer to the specification for the java.lang.management.ThreadMBean
48
# interface - see isThreadContentionMonitoringSupported() method.
51
# To enable thread contention monitoring, uncomment the following line
52
# com.sun.management.enableThreadContentionMonitoring
55
#####################################################################
56
# SNMP Management Properties
57
#####################################################################
59
# If the system property -Dcom.sun.management.snmp.port=<port-number>
61
# - The SNMP agent (with the Java virtual machine MIB) is started
62
# that listens on the specified port for incoming SNMP requests.
63
# - the following properties for read for SNMP management.
65
# The configuration can be specified only at startup time.
66
# Later changes to the above system property (e.g. via setProperty method), this
67
# config file, or the ACL file has no effect to the running SNMP agent.
71
# ##################### SNMP Trap Port #########################
73
# com.sun.management.snmp.trap=<trap-destination-port-number>
74
# Specifies the remote port number at which managers are expected
75
# to listen for trap. For each host defined in the ACL file,
76
# the SNMP agent will send traps at <host>:<trap-destination-port-number>
77
# Default for this property is 162.
80
# To set port for sending traps to a different port use following line
81
# com.sun.management.snmp.trap=<trap-destination-port-number>
85
# ################ SNMP listen interface #########################
87
# com.sun.management.snmp.interface=<InetAddress>
88
# Specifies the local interface on which the SNMP agent will bind.
89
# This is usefull when running on machines which have several
90
# interfaces defined. It makes it possible to listen to a specific
91
# subnet accessible through that interface.
92
# Default for this property is "localhost".
94
# The format of the value for that property is any string accepted
95
# by java.net.InetAddress.getByName(String).
98
# For restricting the port on which SNMP agent listens use following line
99
# com.sun.management.snmp.interface=<InetAddress>
103
# #################### SNMP ACL file #########################
105
# com.sun.management.snmp.acl=true|false
106
# Default for this property is true. (Case for true/false ignored)
107
# If this property is specified as false then the ACL file
108
# is not checked: all manager hosts are allowed all access.
111
# For SNMP without checking ACL file uncomment the following line
112
# com.sun.management.snmp.acl=false
116
# com.sun.management.snmp.acl.file=filepath
117
# Specifies location for ACL file
118
# This is optional - default location is
119
# $JRE/lib/management/snmp.acl
121
# If the property "com.sun.management.snmp.acl" is set to false,
122
# then this property and the ACL file are ignored.
123
# Otherwise the ACL file must exist and be in the valid format.
124
# If the ACL file is empty or non existent then no access is allowed.
126
# The SNMP agent will read the ACL file at startup time.
127
# Modification to the ACL file has no effect to any running SNMP
128
# agents which read that ACL file at startup.
131
#For a non-default acl file location use following line
132
# com.sun.management.snmp.acl.file=filepath
135
#####################################################################
136
# RMI Management Properties
137
#####################################################################
139
# If system property -Dcom.sun.management.jmxremote.port=<port-number>
141
# - A MBean server is started
142
# - JRE Platform MBeans are registered in the MBean server
143
# - RMI connector is published in a private readonly registry at
144
# specified port using a well known name, "jmxrmi"
145
# - the following properties are read for JMX remote management.
147
# The configuration can be specified only at startup time.
148
# Later changes to above system property (e.g. via setProperty method),
149
# this config file, the password file, or the access file have no effect to the
150
# running MBean server, the connector, or the registry.
154
# ###################### RMI SSL #############################
156
# com.sun.management.jmxremote.ssl=true|false
157
# Default for this property is true. (Case for true/false ignored)
158
# If this property is specified as false then SSL is not used.
161
#For RMI monitoring without SSL use the following line
162
# com.sun.management.jmxremote.ssl=false
163
com.sun.management.jmxremote.ssl=false
165
# com.sun.management.jmxremote.ssl.enabled.cipher.suites=<cipher-suites>
166
# The value of this property is a string that is a comma-separated list
167
# of SSL/TLS cipher suites to enable. This property can be specified in
168
# conjunction with the previous property "com.sun.management.jmxremote.ssl"
169
# in order to control which particular SSL/TLS cipher suites are enabled
170
# for use by accepted connections. If this property is not specified then
171
# the SSL RMI Server Socket Factory uses the SSL/TLS cipher suites that
172
# are enabled by default.
175
# com.sun.management.jmxremote.ssl.enabled.protocols=<protocol-versions>
176
# The value of this property is a string that is a comma-separated list
177
# of SSL/TLS protocol versions to enable. This property can be specified in
178
# conjunction with the previous property "com.sun.management.jmxremote.ssl"
179
# in order to control which particular SSL/TLS protocol versions are
180
# enabled for use by accepted connections. If this property is not
181
# specified then the SSL RMI Server Socket Factory uses the SSL/TLS
182
# protocol versions that are enabled by default.
185
# com.sun.management.jmxremote.ssl.need.client.auth=true|false
186
# Default for this property is false. (Case for true/false ignored)
187
# If this property is specified as true in conjunction with the previous
188
# property "com.sun.management.jmxremote.ssl" then the SSL RMI Server
189
# Socket Factory will require client authentication.
192
#For RMI monitoring with SSL client authentication use the following line
193
# com.sun.management.jmxremote.ssl.need.client.auth=true
196
# ################ RMI User authentication ################
198
# com.sun.management.jmxremote.authenticate=true|false
199
# Default for this property is true. (Case for true/false ignored)
200
# If this property is specified as false then no authentication is
201
# performed and all users are allowed all access.
204
# For RMI monitoring without any checking use the following line
205
# com.sun.management.jmxremote.authenticate=false
206
com.sun.management.jmxremote.authenticate=true
209
# ################ RMI Login configuration ###################
211
# com.sun.management.jmxremote.login.config=<config-name>
212
# Specifies the name of a JAAS login configuration entry to use when
213
# authenticating users of RMI monitoring.
215
# Setting this property is optional - the default login configuration
216
# specifies a file-based authentication that uses the password file.
218
# When using this property to override the default login configuration
219
# then the named configuration entry must be in a file that gets loaded
220
# by JAAS. In addition, the login module(s) specified in the configuration
221
# should use the name and/or password callbacks to acquire the user's
222
# credentials. See the NameCallback and PasswordCallback classes in the
223
# javax.security.auth.callback package for more details.
225
# If the property "com.sun.management.jmxremote.authenticate" is set to
226
# false, then this property and the password & access files are ignored.
229
# For a non-default login configuration use the following line
230
# com.sun.management.jmxremote.login.config=<config-name>
231
#com.sun.management.jmxremote.login.config=GridwareConfig
234
# ################ RMI Password file location ##################
236
# com.sun.management.jmxremote.password.file=filepath
237
# Specifies location for password file
238
# This is optional - default location is
239
# $JRE/lib/management/jmxremote.password
241
# If the property "com.sun.management.jmxremote.authenticate" is set to
242
# false, then this property and the password & access files are ignored.
243
# Otherwise the password file must exist and be in the valid format.
244
# If the password file is empty or non-existent then no access is allowed.
247
# For a non-default password file location use the following line
248
# com.sun.management.jmxremote.password.file=filepath
249
com.sun.management.jmxremote.password.file=./util/jmxremote.password
252
# ################ RMI Access file location #####################
254
# com.sun.management.jmxremote.access.file=filepath
255
# Specifies location for access file
256
# This is optional - default location is
257
# $JRE/lib/management/jmxremote.access
259
# If the property "com.sun.management.jmxremote.authenticate" is set to
260
# false, then this property and the password & access files are ignored.
261
# Otherwise, the access file must exist and be in the valid format.
262
# If the access file is empty or non-existent then no access is allowed.
265
# For a non-default password file location use the following line
266
# com.sun.management.jmxremote.access.file=filepath
267
com.sun.management.jmxremote.access.file=./util/jmxremote.access