Broker Properties for JMX Support

Broker configuration properties that support JMX are listed in Table 14–11. None of these properties can be set from the command line with the Message Queue 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, as described below, some of these properties can be set with corresponding Broker utility options.

The imq.jmx.connector.list property defines a set of named JMX connectors to be created at broker startup; imq.jmx.connector.activelist specifies which of these are to be activated. Each named connector then has its own set of properties:

   imq.jmx.connector.connectorName.urlpath
   imq.jmx.connector.connectorName.useSSL
   imq.jmx.connector.connectorName.brokerHostTrusted

By default, two JMX connectors are created, named jmxrmi and ssljmxrmi; the second is configured to use Secure Socket Layer (SSL) encryption (imq.jmx.connector.ssljmxrmi.useSSL = true), while the second is not (imq.jmx.connector.jmxrmi.useSSL = false). By default, only the jmxrmi connector is activated at broker startup; seeSSL Support for JMX Clients, below, for information on how to activate the ssljmxrmi connector for secure communications.

Message Queue’s JMX connectors use remote method invocation (RMI) as the infrastructure for communicating between client and server. The broker properties imq.jmx.rmiregistry.start and imq.jmx.rmiregistry.use specify whether to start a local RMI registry at broker startup or use an external registry. The imq.jmx.rmiregistry.port property specifies the port number for the RMI registry. For convenience, these properties can also be specified by using equivalent Broker utility (imqbrokerd) options at broker startup: -startRmiRegistry, -useRmiRegistry, and -rmiRegistryPort, respectively (see Table 13–1).

The Command utility (imqcmd) subcommand list jmx displays a list of JMX service URLs of JMX connectors created and started at broker startup. This information is needed by JMX clients that do not use the Message Queue convenience class AdminConnectionFactory to obtain their JMX connectors, and can also be used for managing or monitoring Message Queue via a generic JMX browser such as the Java Monitoring and Management Console (jconsole).