Sun Java System Message Queue 4.1 Administration Guide

JMX Properties

The broker properties listed in Table 14–11 support the use of the Java Management Extensions (JMX) application programming interface by Message Queue client programs to configure and monitor Message Queue resources. None of these properties can be set from the command line with the Command utility (imqcmd). Instead, they can either be set at broker startup with the -D option of the Broker utility (imqbrokerd) or edited by hand in the broker's instance configuration file (config.properties). In addition, some of these properties (imq.jmx.rmiregistry.start, imq.jmx.rmiregistry.use, imq.jmx.rmiregistry.port) can be set with corresponding Broker utility options described in Table 13–1.

See Appendix D, JMX Support for further information on administrative support of JMX clients.

Table 14–11 Broker Properties for JMX Support


Property	Type	Default Value	Description
`imq.jmx.connector.list`	String	`jmxrmi,ssljmxrmi`	Names of preconfigured JMX connectors, separated by commas
`imq.jmx.connector.activelist`	String	`jmxrmi`	Names of JMX connectors to be activated at broker startup, separated by commas
`imq.jmx.connector.connectorName.urlpath`	String	See description	`urlPath` component of JMX service URL for connector `connectorName` Useful in cases where the JMX service URL path must be set explicitly (such as when a shared external RMI registry is used). Default value: If an RMI registry is used to store the RMI stub for JMX connectors (`imq.jmx.registry.start` or `imq.jmx.registry.use` set to `true`): `/jndi/rmi://brokerHost:rmiPort` `/brokerHost/brokerPort/connectorName` If an RMI registry is not used (the default case, `imq.jmx.registry.start` and `imq.jmx.registry.use` both `false`): `/stub/rmiStub` where `rmiStub` is an encoded and serialized representation of the RMI stub itself
`imq.jmx.connector.connectorName.useSSL`	Boolean	`false`	Use Secure Socket Layer (SSL) for connector `connectorName`?
`imq.jmx.connector.connectorName.brokerHostTrusted`			Trust any certificate presented by broker for connector `connectorName`?
	Boolean	`false`	Applies only when `imq.jmx.connector.connectorName.useSSL` is `true`. If `false`, the Message Queue 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.
`imq.jmx.rmiregistry.start`	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 it to store the RMI stub for JMX connectors. Note that 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 to the Message Queue Broker utility (`imqbrokerd`).
`imq.jmx.rmiregistry.use`	Boolean	`false`	Use external RMI registry? Applies only if `imq.jmx.rmiregistry.start` is `false`. If `true`, the broker will use an external RMI registry at the port specified by `imq.jmx.rmiregistry.port` to store the RMI stub for JMX connectors. The external RMI registry must already be running at broker startup. For convenience, this property can also be set at broker startup with the `-useRmiRegistry` option to the Message Queue Broker utility (`imqbrokerd`).
`imq.jmx.rmiregistry.port`	Integer	`1099`	Port number of RMI registry Applies only if `imq.jmx.rmiregistry.start` or `imq.jmx.rmiregistry.use` is `true`. JMX connectors can then be configured to use the RMI registry by including this port number in the URL path of their JMX service URLs. For convenience, this property can also be set at broker startup with the `-rmiRegistryPort` option to the Message Queue Broker utility (`imqbrokerd`).