Fuse Message Broker

Managing and Monitoring a Broker

Version 5.5

Febuary 2012
Trademark Disclaimer
Third Party Acknowledgements

Updated: 27 Mar 2014

Table of Contents

1. Introduction
2. Setting up the Administration Tool
Setting up the Windows Environment
Setting up the Unix/Linux/OS X Environment
3. Setting up and Accessing the Fuse Message Broker Web Console
Using the Embedded Console
Deploying a Standalone Console
4. Installing Fuse Message Broker as a Windows Service
Configuring the Wrapper
Installing and Starting the Windows Service
5. Starting a Broker
Specifying the Broker's Configuration
Starting a Broker on Windows
Starting a Broker on Unix/Linux/OS X
Starting a Broker with Maven
6. Shutting Down a Broker
Shutting Down a Broker on Windows
Shutting Down a Broker on Unix/Linux/OS X
7. Using the Advisory Topics
8. Using the Log
9. Using JMX
Configuring JMX
Statistics Collected by JMX
Managing the Broker with JMX
10. Using the Statistics Plug-in
A. Common Problems
B. Administration Tool Commands
activemq — starts a foreground broker on Windows
activemq setup — creates default configurations for the activemq command on Unix, and Unix-like, platforms
activemq start — starts a daemon broker on Unix, and Unix-like, platforms
activemq console — starts a foreground broker on Unix, and Unix-like, platforms
activemq restart — restarts a running broker on Unix, and Unix-like, platforms
activemq status — checks the status of a running broker on Unix, and Unix-like, platforms
activemq stop — shuts down a running broker on Unix, and Unix-like, platforms
activemq-admin start — creates and starts a broker using a configuration file or a broker URI
activemq-admin create — creates a new instance of the broker's file structure
activemq-admin stop — shuts down a running broker
activemq-admin list — lists the available brokers
activemq-admin query — queries the for broker information on specific objects
activemq-admin bstat — summarizes the statistics for a broker
activemq-admin browse — browse the contents of a destination
activemq-admin journal-audit — audits the log files of the AMQ persistence store. It does not work with the KahaDB persistence store.
activemq-admin purge — purges messages from a destination
activemq-admin encrypt — encrypts the specified text
activemq-admin decrypt — decrypts an encrypted message
C. Broker Properties
Index

List of Tables

2.1. Windows Administration Tool Environment Variables
2.2. Unix Administration Tool Environment Variables
5.1. Maven Configuration Properties
9.1. Broker JMX Configuration Properties
9.2. Broker JMX Statistics
9.3. Destination JMX Statistics
9.4. Connection JMX Statistics
9.5. Broker MBean Operations
9.6. Connector MBean Operations
9.7. Network Connector MBean Operations
9.8. Queue MBean Operations
9.9. Topic MBean Operations
9.10. Subscription MBean Operations
B.1. Message Headers for Filtering
C.1. Broker URI Properties
C.2. Property File Properties

List of Examples

2.1. Sample Windows Environment Script
3.1. Jetty Connector Configuration
3.2. Configuring the Web Console's Port
3.3. Disabling the Embedded Web Console
3.4. Configuration for Deploying the Web Console in Tomcat
3.5. Configuration for Monitoring a Cluster with the Web Console
4.1. Default Environment Settings
4.2. Default Java System Properties
4.3. Default Wrapper Application Settings
4.4. Default Wrapper Classpath
5.1. Broker URI Syntax
5.2. Broker URI
5.3. Broker Properties File
5.4. Syntax for Starting a Broker on Windows
5.5. Syntax for Starting a Daemon Broker on Unix
5.6. Syntax for Starting a Foreground Broker on Unix
5.7. Using the Maven Plug-in from the Command Line
5.8. Using the Maven Plug-in from a POM
6.1. Syntax for Stopping a Broker on Windows
6.2. Shutting Down a Broker on Windows
6.3. Shutting Down All Broker on Windows
6.4. Shutting Down a Broker on Windows in a Non-default JMX Context
6.5. Syntax for Stopping a Broker on Unix/Linux/OS X
6.6. Shutting Down a Broker on Unix/Linux/OS X
6.7. Shutting Down All Broker on Unix/Linux/OS X
6.8. Shutting Down a Broker in a Non-default JMX Context on Unix/Linux/OS X
9.1. Configuring a Broker's JMX Connection

There are a number of tools that you can use to monitor and administer Fuse Message Broker.

The following tools are included with Fuse Message Broker:

  • administration tool—a command line tool that can be used to manage a broker and do rudimentary metric reporting

  • Web console—a browser based console that provides metric reporting, destination browsing, and other administrative functions

For more advanced monitoring and management capabilities FuseSource offers Fuse HQ.

In addition to the FuseSource supplied tools there are a number of third party tools that can be used to administer and monitor a broker including:

  • jconsole—a JMX tool that is shipped with the JDK

  • VisualVM—a visual tool integrating several command line JDK tools and lightweight profiling capabilities

Important

The administration tool requires that brokers have JMX enabled. By default, JMX is enabled. For more information see Using JMX.

Table 2.2 describes the environment variables used by the administration tool on Unix and Unix-like platforms.


Tip

The default setting for ACTIVEMQ_OPTS_MEMORY is very low for systems that run under a heavy load. You will want to change this value to provide the broker with more memory.

The Fuse Message Broker Web console is an embedded console for administering your broker, its destination, and the routes deployed in the broker. Using the embedded console is an easy way to manage your broker with minimal configuration.

If you want more security, more reliability, or the ability to monitor master/slave clusters, you can deploy the Web console as a standalone application. It is easy to deploy into Tomcat or any standard Web container.

To change the port at which the embedded Web console is accessed, you need to edit the broker's configuration file to as follows:

The configuration shown in Example 3.2 configures the Web console such that the routing console can be accessed from http://localhost:8563/camel.


Fuse Message Broker uses a wrapper, based on the Java service wrapper from Tanuki Software Ltd., that provides a solution to the problem of launching a Java application as a Windows service. The wrapper provides a mechanism for specifying all of the required JVM and application specific parameters to the Windows' service interface.

The wrapper is located in the bin/win32 folder of a Windows Fuse Message Broker installation. This folder contains the following:

  • activemq.bat—script that starts the broker in the foreground

  • InstallService.bat—script that installs the broker as a Windows service

  • UninstallService.bat—script that uninstalls the broker from the service registry

  • wrapper.conf—file that configures the wrapper service

  • wrapper.dll

  • wrapper.exe—wrapper service executable

Note

FuseSource does support the 64 bit version of the service wrapper. However, due to licensing concerns, you must obtain it directly from Tanuki Software Ltd..

Before using the wrapper to install Fuse Message Broker as a Windows service, you will want to check the wrappers configuration to ensure it is set up properly.

There are three ways to pass configuration to a broker instance at start-up:

  • XBean URI—specifies the location a Spring XML configuration file

  • Broker URI—specifies the broker configuration as part of the URI

  • Properties URI—specifies the location of properties file containing Fuse Message Broker configuration

You can specify a broker's configuration entirely on the command line using a broker URI of the form shown in Example 5.1.


For example, the URI shown in Example 5.2 starts up a broker that accepts connections on port 61616, establishes a network connection to remotehost:61616, and disables persistence.


On Unix, the activemq start command to starts an instance of Fuse Message Broker in the background. The syntax for the command is shown in Example 5.5.


For example, to start a daemon broker using the default broker configuration, enter:

% activemq start xbean:file:conf/activemq.xml

You can optionally disable schema validation of the configuration file using the validate flag, as follows:

% activemq start xbean:file:conf/activemq.xml?validate=false

By default, the daemon broker runs as the current user. It is good practice to specify a special effective user for the broker. This special effective user should be given just enough privileges to run the broker. This provides added security by ensuring that the broker process has limited ability to corrupt sensitive part of your system.

The ACTIVEMQ_USER environment variable specifies the effective user for the broker instances. By default, the broker will run as the currently logged in user. See Setting up the Unix/Linux/OS X Environment.

If the basic broker provided by adding the plug-in on the command line is insufficient for test an application the plug-in can be included in the project's POM. When included in a POM, the Fuse Message Broker plug-in uses a configuration URI to configure the broker. The plug-in can also set system properties when starting the broker.

Table 5.1 describes the configuration properties used by the Fuse Message Broker Maven plug-in.


To start the configured broker when running the project use mvn activemq:run.

Example 5.8 shows a POM fragment that configures the Fuse Message Broker plug-in to start a broker using the activemq.xml configuration file on the project's class path.

Example 5.8. Using the Maven Plug-in from a POM

<project ... >

  ...

  <repositories>
  <!-- FuseSource maven repositories -->
    <repository>
      <id>fusesource.releases</id>
      <name>FuseSoure releases repository</name>
      <url>http://repo.fusesource.com/maven2/</url>
      <releases>
        <enabled>true</enabled>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
    </repository>
    <repository>
      <id>fusesource.snapshots</id>
      <name>FuseSource Snapshot Repository</name>
      <url>http://repo.fusesource.com/maven2-snapshot</url>
      <snapshots>
        <enabled>true</enabled>
      </snapshots>
      <releases>
        <enabled>false</enabled>
      </releases>
    </repository>
  </repositories>

  <pluginRepositories>
  <!-- FuseSource maven repositories -->
    <pluginRepository>
      <id>fusesource.releases</id>
      <name>FuseSoure releases repository</name>
      <url>http://repo.fusesource.com/maven2/</url>
      <releases>
        <enabled>true</enabled>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
    </pluginRepository>
    <pluginRepository>
      <id>fusesource.snapshots</id>
      <name>FuseSource Snapshot Repository</name>
      <url>http://repo.fusesource.com/maven2-snapshot</url>
      <snapshots>
        <enabled>true</enabled>
      </snapshots>
      <releases>
        <enabled>false</enabled>
      </releases>
    </pluginRepository>
  </pluginRepositories>

  ...

  <build>    
    <plugins>
      <plugin>
        <groupId>org.apache.activemq.tooling</groupId>
        <artifactId>maven-activemq-plugin</artifactId>
        <version>5.5</version>
        <configuration>
          <configUri>xbean:activemq.xml</configUri>
          <fork>false</fork>
        </configuration>
        <dependencies>
          <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring</artifactId>
            <version>2.5.5</version>
          </dependency>
          <dependency>
            <groupId>org.mortbay.jetty</groupId>
            <artifactId>jetty-xbean</artifactId>
            <version>6.1.11</version>
          </dependency> 	
          <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-activemq</artifactId>
            <version>1.1.0</version>
          </dependency>
        </dependencies>			
      </plugin>
    </plugins>
  </build>
</project>

Important

The administration tool requires that brokers have JMX enabled. By default, JMX is enabled. For more information see Using JMX.

On Windows, the command to shutdown a broker is activemq-admin stop. The syntax for the command is shown in Example 6.1.


If you do not use the --jmxurl parameter, the default JMX url, service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi, is used. This is the JMX url specified in the default Fuse Message Broker configuration.

If you configured a broker to use a different JMX url, you must use the --jmxurl parameter and provide the JMX url for connecting to the broker.

Tip

If you have a broker running as a Windows service and have JMX turned on, you can use activemq-admin stop to shut it down. However, the recommended way to shut down a broker running as a Windows service is documented in Stopping the broker manually.

If you have secured JMX access to the broker, you will need to use the -jmxuser and -jmxpassword parameters. They specify the user name and password required to access the broker's JMX context. For information about using security with JMX see JMX Security in Security Guide.

On Unix and Unix-like systems, the command to shutdown a broker is activemq stop. The syntax for the command is shown in Example 6.5.


If you do not use the --jmxurl parameter, the default JMX url, service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi, is used. This is the JMX url specified in the default Fuse Message Broker configuration.

If you configured a broker to use a different JMX url, you must use the --jmxurl parameter and provide the JMX url for connecting to the broker.

If you have secured JMX access to the broker, you will need to use the -jmxuser and -jmxpassword parameters. They specify the user name and password required to access the broker's JMX context. For information about using security with JMX see JMX Security in Security Guide.

By default Fuse Message Broker creates MBeans, loads them into the MBean server created by the JVM, and creates a dedicated JMX connector that provides a Fuse Message Broker-specific view of the MBean server. The default settings are sufficient for simple deployments and make it easy to access the statistics and management operations provided by a broker. For more complex deployments you easily configure many aspects of how a broker configures itself for access through JMX. For example, you can change the JMX URI of the JMX connector created by the broker or force the broker to use the generic JMX connector created by the JVM.

By connecting a JMX aware management and monitoring tool to a broker's JMX connector, you can view detailed information about the broker. This information provides a good indication of broker health and potential problem areas. In addition to the collected statistics, Fuse Message Broker's JMX interface provides a number of operations that make it easy to manage a broker instance. These include stopping a broker, starting and stopping network connectors, and managing destinations.

If the default JMX behavior is not appropriate for your deployment environment, you can customize how the broker exposes its MBeans. To customize a broker's JMX configuration, you add a managementContext child element to the broker's broker element. The managementContext element uses a managementContext child to configure the broker. The attributes of the inner managementContext element specify the broker's JMX configuration.

Table 9.1 describes the configuration properties for controlling a broker's JMX behavior.


Example 9.1 shows configuration for a broker that will only use the JVM's MBean server and will not create its own JMX connector.


Table 9.3 describes the statistics collected for a destination.

Table 9.3. Destination JMX Statistics

NameDescription
BlockedProducerWarningIntervalSpecifies, in milliseconds, the interval between warnings issued when a producer is blocked from adding messages to the destination.
MemoryLimitSpecifies the memory limit, in bytes, used for holding undelivered messages before paging to temporary storage.
MemoryPercentageUsedSpecifies the percentage of available memory in use.
MaxPageSizeSpecifies the maximum number of messages that can be paged into the destination.
CursorFullSpecifies if the cursor has reached its memory limit for paged messages.
CursorMemoryUsageSpecifies, in bytes, the amount of memory the cursor is using.
CursorPercentUsageSpecifies the percentage of the cursor's available memory is in use.
EnqueueCountSpecifies the number of messages that have been sent to the destination.
DequeueCountSpecifies the number of messages that have been acknowledged and removed from the destination.
DispatchCountSpecifies the number of messages that have been delivered to consumers, but not necessarily acknowledged by the consumer.
InFlightCountSpecifies the number of dispatched to, but not acknowledged by, consumers.
ExpiredCountSpecifies the number of messages that have expired in the destination.
ConsumerCountSpecifies the number of consumers that are subscribed to the destination.
QueueSizeSpecifies the number of messages in the destination that are waiting to be consumed.
AverageEnqueueTimeSpecifies the average amount of time, in milliseconds, that messages sat in the destination before being consumed.
MaxEnqueueTimeSpecifies the longest amount of time, in milliseconds, that a message sat in the destination before being consumed.
MinEnqueueTimeSpecifies the shortest amount of time, in milliseconds, that a message sat in the destination before being consumed.
MemoryUsagePortionSpecifies the portion of the broker's memory limit used by the destination.
ProducerCountSpecifies the number of producers connected to the destination.

Table 9.5 describes the operations exposed by the MBean for a broker.

Table 9.5. Broker MBean Operations

OperationDescription
void start(); Starts the broker. In reality this operation is not useful because you cannot access the MBeans if the broker is stopped.
void stop(); Forces a broker to shut down. There is no guarantee that all messages will be properly recorded in the persistent store.
void stopGracefully(String queueName); Checks that all listed queues are empty before shutting down the broker.
void enableStatistics(); Activates the broker's statistics plug-in.
void resetStatistics(); Resets the data collected by the statistics plug-in.
void disableStatistics(); Deactivates the broker's statistics plug-in.
String addConnector(String URI); Adds a transport connector to the broker and starts it listening for incoming client connections and returns the name of the connector.
boolean removeConnector(String connectorName); Deactivates the specified transport connector and removes it from the broker.
String addNetworkConnector(String URI); Adds a network connector to the specified broker and returns the name of the connector.
boolean removeNetworkConnector(String connectorName); Deactivates the specified connector and removes it from the broker.
void addTopic(String name); Adds a topic destination to the broker.
void addQueue(String name); Adds a queue destination to the broker.
void removeTopic(String name); Removes the specified topic destination from the broker.
void removeQueue(String name); Removes the specified queue destination from the broker.
ObjectName createDurableSubscriber(String clientId,
                                   String subscriberId,
                                   String topicName,
                                   String selector);
Creates a new durable subscriber.
void destroyDurableSubscriber(String clientId,
                              String subscriberId);
Destroys a durable subscriber.
void gc(); Runs the JVM garbage cleaner.
void terminateJVM(int exitCode); Shuts down the JVM.
void reloadLog4jProperties(); Reloads the logging configuration from log4j.properties.

Table 9.8 describes the operations exposed by the MBean for a queue destination.

Table 9.8. Queue MBean Operations

OperationDescription
CompositeData getMessage(String messageId); Returns the specified message from the queue without moving the message cursor.
void purge(); Deletes all of the messages from the queue.
boolean removeMessage(String messageId); Deletes the specified message from the queue.
int removeMatchingMessages(String selector); Deletes the messages matching the selector from the queue and returns the number of messages deleted.
int removeMatchingMessages(String selector,
                           int maxMessages);
Deletes up to the maximum number of messages that match the selector and returns the number of messages deleted.
boolean copyMessageTo(String messageId,
                      String destination);
Copies the specified message to a new destination.
int copyMatchingMessagesTo(String selector,
                           String destination);
Copies the messages matching the selector and returns the number of messages copied.
int copyMatchingMessagesTo(String selector,
                           String destination,
                           int maxMessages);
Copies up to the maximum number of messages that match the selector and returns the number of messages copied.
boolean moveMessageTo(String messageId,
                      String destination);
Moves the specified message to a new destination.
int moveMatchingMessagesTo(String selector,
                           String destination);
Moves the messages matching the selector and returns the number of messages moved.
int moveMatchingMessagesTo(String selector,
                           String destination,
                           int maxMessages);
Moves up to the maximum number of messages that match the selector and returns the number of messages moved.
boolean retryMessage(String messageId); Moves the specified message back to its original destination.
int cursorSize(); Returns the number of messages available to be paged in by the cursor.
boolean doesCursorHaveMessagesBuffered(); Returns true if the cursor has buffered messages to be delivered.
boolean doesCursorHaveSpace(); Returns true if the cursor has memory space available.
CompositeData[] browse(); Returns all messages in the queue, without changing the cursor, as an array.
CompositeData[] browse(String selector); Returns all messages in the queue that match the selector, without changing the cursor, as an array.
TabularData browseAsTable(String selector); Returns all messages in the queue that match the selector, without changing the cursor, as a table.
TabularData browseAsTable(); Returns all messages in the queue, without changing the cursor, as a table.
void resetStatistics(); Resets the statistics collected for the queue.
java.util.List browseMessages(String selector); Returns all messages in the queue that match the selector, without changing the cursor, as a list.
java.util.List browseMessages(); Returns all messages in the queue, without changing the cursor, as a list.
String sendTextMessage(String body,
                       String username,
                       String password);
Send a text message to a secure queue.
String sendTextMessage(String body); Send a text message to a queue.

activemq — starts a foreground broker on Windows
activemq setup — creates default configurations for the activemq command on Unix, and Unix-like, platforms
activemq start — starts a daemon broker on Unix, and Unix-like, platforms
activemq console — starts a foreground broker on Unix, and Unix-like, platforms
activemq restart — restarts a running broker on Unix, and Unix-like, platforms
activemq status — checks the status of a running broker on Unix, and Unix-like, platforms
activemq stop — shuts down a running broker on Unix, and Unix-like, platforms
activemq-admin start — creates and starts a broker using a configuration file or a broker URI
activemq-admin create — creates a new instance of the broker's file structure
activemq-admin stop — shuts down a running broker
activemq-admin list — lists the available brokers
activemq-admin query — queries the for broker information on specific objects
activemq-admin bstat — summarizes the statistics for a broker
activemq-admin browse — browse the contents of a destination
activemq-admin journal-audit — audits the log files of the AMQ persistence store. It does not work with the KahaDB persistence store.
activemq-admin purge — purges messages from a destination
activemq-admin encrypt — encrypts the specified text
activemq-admin decrypt — decrypts an encrypted message

Important

The administration tool requires that brokers have JMX enabled. By default, JMX is enabled. For more information see Using JMX.

Name

activemq-admin query — queries the for broker information on specific objects

Synopsis

activemq-admin query [-QMBeanType=name] [-xQMBeanType=name] [--objname query] [--xobjname query] [--view {attr...}] [--jmxurl JMXUrl] [-jmxuser userName] [-jmxpassword password] [-Dname=value...] [--version] [[--help] | [-h] | [-?]]

Name

activemq-admin browse — browse the contents of a destination

Synopsis

activemq-admin browse {--amqurl brokerURL} [--msgsel {msgsel...}] [--view {attr...}] [[-Vheader] | [-Vcustom] | [-Vbody]] [--version] [[--help] | [-h] | [-?]] destName

Name

activemq-admin journal-audit — audits the log files of the AMQ persistence store. It does not work with the KahaDB persistence store.

Synopsis

activemq-admin journal-audit [--message-format=VelocityTemplate] [--topic-ack-format=VelocityTemplate] [--queue-ack-format=VelocityTemplate] [--transaction-format=VelocityTemplate] [--trace-format=VelocityTemplate] [--where=JoSQLExp] [-Dname=value...] [--version] [[--help] | [-h] | [-?]] journalDir

B

BlockedProducerWarningInterval, Destination statistics
broker
addConnector, Broker actions
addNetworkConnector, Broker actions
addQueue, Broker actions
addTopic, Broker actions
createDurableSubscriber, Broker actions
destroyDurableSubscriber, Broker actions
disableStatistics, Broker actions
effective user, Environment variables, Starting a background broker
enableStatistics, Broker actions
gc, Broker actions
reloadLog4jProperties, Broker actions
removeConnector, Broker actions
removeNetworkConnector, Broker actions
removeQueue, Broker actions
removeTopic, Broker actions
resetStatistics, Broker actions
start, Broker actions
stop, Broker actions
stopGracefully, Broker actions
terminateJVM, Broker actions
useJmx, Enabling and disabling
broker uri, Broker URI
BrokerId, Broker statistics
brokerId, Global properties
BrokerName, Broker statistics
brokerName, Global properties
BrokerVersion, Broker statistics

C

configuration
broker uri, Broker URI
properties file, Property configuration
xbean, XBean configuration
configuration uri
broker, Broker URI
properties, Property configuration
xbean, XBean configuration
configUri, Using the POM
connector
connectionCount, Connector actions
disableStatistics, Connector actions
enableStatistics, Connector actions
resetStatistics, Connector actions
start, Connector actions
stop, Connector actions
connectorHost, Advanced configuration
connectorPath, Advanced configuration
connectorPort, Advanced configuration
ConsumerCount, Destination statistics
createConnector, Advanced configuration
createMBeanServer, Advanced configuration
CursorFull, Destination statistics
CursorMemoryUsage, Destination statistics
CursorPercentUsage, Destination statistics

D

DataDirectory, Broker statistics
deleteAllMessagesOnStartup, Global properties
DequeueCount, Destination statistics
DequeueCounter, Subscription statistics
DispatchCount, Destination statistics
DispatchedCounter, Subscription statistics
DispatchedQueueSize, Subscription statistics

E

embedded console
disabling, Disabling the embedded console
enableStatistics, Global properties
EnqueueCount, Destination statistics
EnqueueCounter, Subscription statistics
ExpiredCount, Destination statistics

F

forced shutdown, Shutdown timeout
fork, Using the POM
Fuse HQ, Tools

I

InFlightCount, Destination statistics

J

jconsole, Tools
JMX
disabling, Enabling and disabling
jmxDomainName, Advanced configuration

K

kill timeout, Shutdown timeout

M

managementContext, Advanced configuration
connectorHost, Advanced configuration
connectorPath, Advanced configuration
connectorPort, Advanced configuration
createConnector, Advanced configuration
createMBeanServer, Advanced configuration
jmxDomainName, Advanced configuration
rmiServerPort, Advanced configuration
useMBeanServer, Advanced configuration
maven-activemq-plugin
command line, Using the command line
in a POM, Using the POM
MaxEnqueueTime, Destination statistics
MaximumPendingMessageLimit, Subscription statistics
MaxPageSize, Destination statistics
MemoryLimit, Broker statistics, Destination statistics
MemoryPercentageUsed, Broker statistics, Destination statistics
MemoryUsagePortion, Destination statistics
MessageCountAwaitingAcknowledge, Subscription statistics
MinEnqueueTime, Destination statistics

N

network connector
start, Network connector actions
stop, Network connector actions
networkConnectors, Property file specific

P

PendingQueueSize, Subscription statistics
persistent, Global properties
populateJMSXUserID, Global properties
PrefetchSize, Subscription statistics
ProducerCount, Destination statistics
properties uri, Property configuration

Q

queue
browse, Queue actions
browseAsTable, Queue actions
browseMessages, Queue actions
copyMatchingMessagesTo, Queue actions
copyMessageTo, Queue actions
cursorSize, Queue actions
doesCursorHaveMessagesBuffered, Queue actions
doesCursorHaveSpace, Queue actions
getMessage, Queue actions
moveMatchingMessagesTo, Queue actions
moveMessageTo, Queue actions
purge, Queue actions
removeMatchingMessages, Queue actions
removeMessage, Queue actions
resetStatistics, Queue actions
retryMessage, Queue actions
sendTextMessage, Queue actions
QueueSize, Destination statistics

R

rmiServerPort, Advanced configuration
routine tasks, Routine tasks
routing console
port number, Changing the port
securing, Securing the console
url, Accessing the console

S

SSL_OPTS, Environment variables
StoreLimit, Broker statistics
StorePercentageUsed, Broker statistics
subscription
browse, Subscription actions
browseAsTable, Subscription actions
cursorSize, Subscription actions
destory, Subscription actions
doesCursorHaveMessagesBuffered, Subscription actions
doesCursorHaveSpace, Subscription actions
isMatchingQueue, Subscription actions
isMatchingTopic, Subscription actions
systemProperties, Using the POM

T

TempLimit, Broker statistics
TempPercentageUsed, Broker statistics
tooling, Tools
topic
browse, Topic actions
browseAsTable, Topic actions
browseMessages, Topic actions
resetStatistics, Topic actions
sendTextMessage, Topic actions
TotalConsumerCount, Broker statistics
TotalDequeueCount, Broker statistics
TotalEnqueueCount, Broker statistics
TotalMessageCount, Broker statistics
TotalProducerCount, Broker statistics
transportConnectors, Property file specific

V

VisualVM, Tools

W

Web console
accessing, Accessing the console
clusters, Monitoring clusters
port number, Changing the port
securing, Securing the console
webconsole.jms.url, Configuring Tomcat, Monitoring clusters
webconsole.jmx.password, Configuring Tomcat
webconsole.jmx.url, Configuring Tomcat, Monitoring clusters
webconsole.jmx.user, Configuring Tomcat