The broker properties listed in Table 16–12 support the use of the Java Management Extensions (JMX) application programming interface by Java applications. The JMX API is used to configure and monitor broker resources.
These JMX-related properties can be set in the broker's instance configuration file (config.properties) or at broker startup with the -D option of the Broker utility (imqbrokerd). None of these properties can be set dynamically with the Command utility (imqcmd).
In addition, some of these properties (imq.jmx.rmiregistry.start, imq.jmx.rmiregistry.use, imq.jmx.rmiregistry.port) can be set with corresponding Broker utilityimqbrokerd options described in Table 15–1.
See Appendix D, JMX Support for further information on administrative support of JMX clients.
Table 16–12 Broker Properties for JMX Support
Property |
Type |
Default Value |
Description |
---|---|---|---|
String |
jmxrmi |
Names of JMX connectors to be activated at broker startup, separated by commas |
|
String |
Shown in next column |
urlpath component of JMX service URL for connector connectorName Useful in cases where an RMI registry is being used and the JMX service URL path must be set explicitly (such as when a shared external RMI registry is used). See The JMX Service URL. Default: /jndi/rmi://brokerHost:rmiPort /brokerHost/brokerPort/connectorName |
|
Integer |
None: the port is dynamically allocated |
Port number of JMX connector Used to specify a static/known JMX connector port, typically in cases where a JMX client is accessing the broker's MBean server through a firewall. See JMX Connections Through a Firewall. |
|
Boolean |
false |
Use Secure Socket Layer (SSL) for connector connectorName? This property is set to true for the ssljmxrmi connector. |
|
Boolean |
false |
Trust any certificate presented by broker for connector connectorName? Applies only when imq.jmx.connector.connectorName.useSSL is true. If false, the JMX client runtime will validate all certificates presented to it. Validation will fail if the signer of the certificate is not in the client's trust store. If true, validation of certificates is skipped. This can be useful, for instance, during software testing when a self-signed certificate is used. |
|
Boolean |
false |
Start RMI registry at broker startup? If true, the broker will start an RMI registry at the port specified by imq.jmx.rmiregistry.port and use the regsitry to store the JMX connector stub. (The value of imq.jmx.rmiregistry.use is ignored in this case.) For convenience, this property can also be set at broker startup with the -startRmiRegistry option ofimqbrokerd. |
|
Boolean |
false |
Use an existing RMI registry? Applies only if imq.jmx.rmiregistry.start is false. If true, the broker will use an existing RMI registry on the local host at the port specified by imq.jmx.rmiregistry.port to store the JMX connector stub. The existing RMI registry must already be running at broker startup. For convenience, this property can also be set at broker startup with the -useRmiRegistry option ofimqbrokerd. |
|
Integer |
1099 |
Port number of RMI registry Applies only if imq.jmx.rmiregistry.start is true or imq.jmx.rmiregistry.use is true. This port number will be included in the URL path of the JMX service URL. For convenience, this property can also be set at broker startup with the -rmiRegistryPort option of imqbrokerd. |