This chapter provides reference information about configuration properties for a message broker. It consists of the following sections:
Table 17-1 lists the broker properties related to connection services.
Table 17-1 Broker Connection Properties
Property | Type | Default Value | Description |
---|---|---|---|
|
String |
None |
Broker identifier For brokers using a shared JDBC-based data store, this string is appended to the names of all database tables to identify each table with a particular broker. Must be a unique alphanumeric string of no more than n - 13 characters, where n is the maximum table name length allowed by the database. This property is unnecessary for an embedded database or a standalone database which stores data for only one broker instance. Note: For enhanced broker clusters ( |
|
String |
|
List of connection services to be activated at broker startup, separated by commas See Table 6-1 under Configuring Connection Services for the names of the available connection services. |
|
String |
All available IP addresses |
Default host name or IP address for all connection services |
|
String |
None |
Host name or IP address of Port Mapper If specified, overrides |
|
Integer |
|
Port number of Port Mapper Note: If multiple broker instances are running on the same host, each must be assigned a unique Port Mapper port. |
|
String |
None |
Host name or IP address for connection service If specified, overrides |
|
Integer |
|
Port number for connection service A value of |
|
Integer |
|
Maximum number of pending Port Mapper requests in operating system backlog |
|
String |
|
Threading model for thread pool management:
|
The dedicated model limits the number of connections that can be supported, but provides higher performance; the shared model increases the number of possible connections, but at the cost of lower performance because of the additional overhead needed for thread management. |
|||
|
Integer |
|
Minimum number of threads maintained in connection service's thread pool When the number of available threads exceeds this threshold, threads will be shut down as they become free until the minimum is reached. The default value varies by connection service, as shown. |
|
Integer |
|
Number of threads beyond which no new threads are added to the thread pool for use by the named connection service Must be greater than The default value varies by connection service, as shown. |
|
Integer |
Solaris: |
Maximum number of connections monitored by a distributor thread The system allocates enough distributor threads to monitor all connections. The smaller the value of this property, the faster threads can be assigned to active connections. A value of The default value varies by operating-system platform, as shown. |
|
Integer |
|
Interval, in seconds, at which to test connection between client and broker A value of |
Footnote 1 Must have the same value for all brokers in an enhanced cluster.
Footnote 2 Can be used with imqcmd
update
bkr
command
Footnote 3 jms
, ssljms
, admin
, and ssladmin
services only; see HTTP/HTTPS Support for information on configuring the httpjms
and httpsjms
services
Footnote 4 jms
and admin
services only
Footnote 5 Shared threading model only
This section includes the following tables:
Table 17-2 lists the broker properties related to routing and delivery services
Table 17-3 lists the broker properties that configure the automatic creation of destinations
Table 17-4 lists the broker properties that configure the administrative creation of destinations
Table 17-2 Broker Routing and Delivery Properties
Property | Type | Default Value | Description |
---|---|---|---|
|
Integer |
|
Maximum number of messages held by broker A value of |
|
String |
|
Maximum total size of messages held by broker The value may be expressed in bytes, kilobytes, or megabytes, using the following suffixes:
|
An unsuffixed value is expressed in bytes; a value of |
|||
Examples:
|
|||
|
String |
|
Maximum size of a single message body The syntax is the same as for |
|
Integer |
|
Interval, in seconds, at which expired messages are removed |
|
Integer |
|
Percent utilization at which memory resource state is triggered (where resourceState is |
|
Integer |
|
Maximum number of incoming messages allowed in a batch before checking whether memory resource state threshold has been reached (where resourceState is This limit throttles back message producers as system memory becomes increasingly scarce. |
|
Boolean |
|
Remove message body before storing in dead message queue? If |
|
Boolean |
|
Automatically roll back distributed transactions left in prepared state at broker startup? If |
|
Integer |
|
The maximum number of messages that a producer can process in a single transaction. It is recommended that the value be less than 5000 to prevent the exhausting of resources. |
|
Integer |
|
The maximum number of messages that a consumer can process in a single transaction. It is recommended that the value be less than 1000 to prevent the exhausting of resources. |
Footnote 1 Can be used with imqcmd
update
bkr
command
This table lists properties that configure the automatic creation of destinations.
Table 17-3 Broker Properties for Auto-Created Destinations
Property | Type | Default Value | Description |
---|---|---|---|
Boolean |
|
Allow auto-creation of queue destinations? |
|
|
Boolean |
|
Allow auto-creation of topic destinations? |
|
Integer |
120 seconds |
The delay, in seconds. before which auto-created destinations are removed from the system when they no longer have consumers nor contain messages, . A smaller value means that memory reclamation takes place more often. |
|
Integer |
|
Maximum number of unconsumed messages A value of Note: When flow control is in effect ( |
|
String |
|
Maximum size, in bytes, of any single message The value may be expressed in bytes, kilobytes, or megabytes, using the following suffixes:
|
An unsuffixed value is expressed in bytes; a value of |
|||
Examples:
|
|||
|
String |
|
Maximum total memory, in bytes, for unconsumed messages The syntax is the same as for |
|
String |
|
Broker behavior when memory-limit threshold reached:
When |
If the value is |
|||
|
Integer |
|
Maximum number of message producers for destination When this limit is reached, no new producers can be created. A value of |
|
Integer |
|
Maximum number of active message consumers in load-balanced delivery from queue destination A value of |
|
Integer |
|
Maximum number of backup message consumers in load-balanced delivery from queue destination A value of |
|
Integer |
|
Maximum number of messages delivered to queue consumer in a single batch In load-balanced queue delivery, this is the initial number of queued messages routed to active consumers before load balancing begins. A destination consumer can override this limit by specifying a lower value on a connection. A value of |
|
Integer |
|
Maximum number of messages delivered to topic consumer in a single batch A value of Not used when the JMS resource adapter, jmsra, is used to consume messages in a GlassFish Server cluster. |
|
Integer |
|
Maximum number of messages delivered to topic consumer in a single batch when the JMS resource adapter, jmsra, is used to consume messages in a GlassFish Server cluster A value of |
|
Boolean |
|
Local delivery only? This property applies only to destinations in broker clusters, and cannot be changed once the destination has been created. If |
|
Boolean |
|
Local delivery preferred? This property applies only to load-balanced queue delivery in broker clusters. If |
|
Boolean |
|
Send dead messages to dead message queue? If |
|
Boolean |
|
XML schema validation is enabled? If set to |
|
String |
null |
Space separated list of XML schema document (XSD) URI strings The URIs point to the location of one or more XSDs to use for XML schema validation, if enabled. Use double quotes around this value if multiple URIs are specified. Example: " If this property is not set or null and XML validation is enabled, XML validation is performed using a DTD specified in the XML document. |
|
Boolean |
|
Reload XML schema on failure enabled? If set to false or not set, then the schema is not reloaded if validation fails. |
Footnote 1 Can be used with imqcmd
update
bkr
command
Footnote 2 Queue destinations only
Footnote 3 Topic destinations only
This table lists properties that apply to all administratively created destinations. They cannot be configured on individual administratively created destinations.
Table 17-4 Broker Properties for Admin-Created Destinations
Property | Type | Default Value | Description |
---|---|---|---|
|
Integer |
|
Maximum number of messages delivered to topic consumer in a single batch when the JMS resource adapter, jmsra, is used to consume messages in a GlassFish Server cluster A value of |
Message Queue supports both file-based and JDBC-based persistence modules. The broker property imq.persist.store
(Table 17-5) specifies which module to use. The following sections describe the broker configuration properties for the two modules.
Table 17-5 Global Broker Persistence Property
Property | Type | Default Value | Description |
---|---|---|---|
|
String |
|
Module used for persistent data storage:
Must be set to |
Table 17-6 lists the broker properties related to file-based persistence.
Table 17-6 Broker Properties for File-Based Persistence
Property | Type | Default Value | Description |
---|---|---|---|
|
String |
|
Maximum-size message to add to message storage file Any message exceeding this size will be stored in a separate file of its own. |
The value may be expressed in bytes, kilobytes, or megabytes, using the following suffixes:
An unsuffixed value is expressed in bytes. |
|||
Examples:
|
|||
|
Integer |
|
Maximum number of free files available for reuse in destination file pool Free files in excess of this limit will be deleted. The broker will create and delete additional files in excess of the limit as needed. The higher the limit, the faster the broker can process persistent data. |
|
Integer |
|
Percentage of files in free file pools to be maintained in a clean (empty) state The higher this value, the less disk space is required for the file pool, but the more overhead is needed to clean files during operation. |
|
Boolean |
|
Clean up files in free file pools on shutdown? Setting this property to |
|
Boolean |
|
Synchronize in-memory state with physical storage device? Setting this property to Note: If running Oracle Solaris Cluster and its Data Service for Message Queue, set this property to |
|
Boolean |
|
Use memory-mapped file to store transaction data? Setting this property to |
Table 17-7 lists the file-based persistence properties for the transaction logging mechanism.
Table 17-7 Broker Properties for File-Based Persistence Using the Transaction Logging Mechanism
Property | Type | Default Value | Description |
---|---|---|---|
|
Boolean |
|
Enables the transaction logging mechanism. For information about this mechanism, see Optimizing File-Based Transaction Persistence. |
|
Boolean |
|
This property is applicable only if Can improve performance if
|
|
Boolean |
|
This property is applicable only if Overrides the behavior for persisting non-transacted messages (as defined by the
|
|
Boolean |
|
This property is applicable only if Overrides the behavior for persisting non-transacted message acknowledgements (as defined by the
|
Table 17-8 lists the broker properties related to JDBC-based persistence. The first of these properties, imq.persist.jdbc.dbVendor
, identifies the database vendor being used for the broker's persistent data store; all of the remaining properties are qualified by this vendor name.
Table 17-8 Broker Properties for JDBC-Based Persistence
Property | Type | Default Value | Description |
---|---|---|---|
|
String |
None |
Name of database vendor for persistent data store:
|
|
Integer |
300 |
The interval in seconds between attempts to close unnecessary database connections. |
|
Integer |
5 |
The maximum number of connections that should be opened to the database. The Message Queue database connection pool manager uses this value as a guide when creating new connections to the database. |
|
Integer |
5 |
The number of connections that are opened to the database when the Message Queue database connection pool is initialized, and the minimum number of connections that are to be kept open when unnecessary connections are closed. |
|
Boolean |
|
Should the Message Queue database connection pool manager considers the age of a connection in the pool? When
|
|
Boolean |
|
Should the Message Queue database connection pool manager perform extra validation when it gets a connection from the pool? Normally, the pool manager validates a connection it gets from the pool by checking whether the connection is closed and, if possible, by checking whether a connection error has occurred on the connection. When this property is set to
Regardless of the value of this property, Message Queue relies on the underlying JDBC driver to return a good connection when it needs to create a new connection through the driver. Therefore, you should set |
|
String |
per vendor |
The validation query for the Message Queue database connection pool manager to use when |
|
Integer |
|
The maximum number of connections that can be opened to the database. This property is deprecated and may become unsupported in a future release of Message Queue. |
|
String |
per vendor |
Java class name of JDBC driver, if needed, for connecting to database from vendor vendorName |
|
String |
None |
URL for connecting to existing database from vendor vendorName Applicable when driver is used to connect to database. |
|
String |
None |
URL for creating new database from vendor vendorName Applies for embedded database, such as Java DB. |
|
String |
None |
URL for closing connection to database from vendor vendorName Applies for some embedded databases, such as Java DB. |
|
String |
None |
User name, if required, for connecting to database from vendor vendorName For security reasons, the value can instead be specified using command line options |
|
Boolean |
|
Does database from vendor vendorName require a password for broker access? If |
String |
None |
Password, if required, for connecting to database from vendor vendorName |
|
|
String |
None |
Vendor-specific property propName for database from vendor vendorName |
|
String |
None |
Vendor-specific options passed to the database when creating the table schema. |
Footnote 1 Optional
Footnote 2 Should be used only in password files
Table 17-9 lists broker properties related to security services: authentication, authorization, and encryption. Table 17-10 lists broker properties related specifically to file-based authentication, Table 17-11 lists broker properties related specifically to LDAP-based authentication, and Table 17-12 lists broker properties related specifically to JAAS-based authentication.
Table 17-9 Broker Security Properties
Property | Type | Default Value | Description |
---|---|---|---|
|
String |
|
Type of user authentication:
|
|
String |
|
Password encoding method:
|
|
String |
None |
Password encoding method for connection service serviceName:
If specified, overrides |
|
Integer |
|
Interval, in seconds, to wait for client response to authentication requests |
|
Boolean |
|
Use access control? If |
|
String |
|
Specifies the access control type |
|
Boolean |
None |
Use access control for connection service? If specified, overrides If |
|
String |
|
Path to the access control directory |
|
String |
|
Name of access control file The file name specifies a path relative to |
|
String |
None |
Name of access control file for connection service If specified, overrides The file name specifies a path relative to |
|
String |
Not set |
The location, as a URL, of the access control file. If the URL uses LDAP protocol ( |
|
String |
None |
The location, as a URL, of the access control file for the connection service. If specified, overrides If the URL uses LDAP protocol ( |
|
String |
|
Path to directory containing key store file |
|
String |
|
Name of key store file |
|
String |
None |
Password for key store file |
|
Boolean |
|
Obtain passwords from password file? |
|
String |
|
Path to directory containing password file |
|
String |
|
Name of password file |
|
String |
None |
Password for administrative user The Command utility ( |
|
Boolean |
|
Is audit logging to broker log file enabled? |
|
Boolean |
|
Is audit logging to the Solaris BSM audit log disabled? |
Footnote 1 To be used only in password files
Table 17-10 lists broker properties related to user authentication when using a flat-file user repository.
Table 17-10 Broker Security Properties for Flat-File Authentication
Property | Type | Default Value | Description |
---|---|---|---|
|
String |
|
Path to the directory containing the flat-file user repository |
|
String |
|
Name of the flat-file user repository file in the directory specified by |
Table 17-11 lists broker properties related to LDAP-based user authentication.
Table 17-11 Broker Security Properties for LDAP Authentication
Property | Type | Default Value | Description |
---|---|---|---|
|
String |
None |
Host name and port number for LDAP server The value is of the form
where hostName is the fully qualified DNS name of the host running the LDAP server and port is the port number used by the server. |
To specify a list of failover servers, use the following syntax:
|
|||
Entries in the list are separated by spaces. Note that each failover server address is prefixed with |
|||
|
String |
None |
Distinguished name for binding to LDAP user repository Not needed if the LDAP server allows anonymous searches. |
|
String |
None |
Password for binding to LDAP user repository Not needed if the LDAP server allows anonymous searches. |
|
|||
|
String |
None |
Directory base for LDAP user entries |
|
String |
None |
Provider-specific attribute identifier for LDAP user name |
|
String |
None |
When set to a value of Also, the broker extracts the value of the If not set, then normal username format is used. |
|
String |
None |
JNDI filter for LDAP user searches |
|
Boolean |
|
Enable LDAP group searches? Note: Message Queue does not support nested groups. |
|
String |
None |
Directory base for LDAP group entries |
|
String |
None |
Provider-specific attribute identifier for LDAP group name |
|
String |
None |
Provider-specific attribute identifier for user names in LDAP group |
|
String |
None |
JNDI filter for LDAP group searches |
|
Integer |
|
Time limit for LDAP searches, in seconds |
|
Boolean |
|
Use SSL when communicating with LDAP server? |
|
String |
|
The fully qualified class name of the socket factory to use to make SSL connections to the LDAP server. When this property is not set and |
Footnote 1 Should be used only in password files
Footnote 2 Optional
Table 17-12 lists broker properties related to JAAS-based user authentication.
Table 17-12 Broker Security Properties for JAAS Authentication
Property | Type | Default Value | Description |
---|---|---|---|
|
String |
None |
Set to the name of the desired entry (in the JAAS configuration file) that references the login modules you want to use as the authentication service. |
|
String |
None |
This property, used by Message Queue access control, specifies the |
|
String |
None |
This property, used by Message Queue access control, specifies the |
Table 17-13 lists the broker properties related to monitoring services.
Table 17-13 Broker Monitoring Properties
Property | Type | Default Value | Description |
---|---|---|---|
|
String |
|
Logging level Specifies the categories of logging information that can be written to an output channel. Possible values, from high to low:
Each level includes those above it (for example, |
|
Boolean |
|
Log information about dead messages? If
|
|
String |
|
Destination for console output:
|
|
String |
|
Categories of logging information to write to console:
The |
|
String |
|
Path to directory containing log file |
|
String |
|
Name of log file |
|
String |
|
Categories of logging information to write to log file:
The |
|
Integer |
|
File length, in bytes, at which output rolls over to a new log file A value of |
|
Integer |
|
Age of file, in seconds, at which output rolls over to a new log file A value of |
|
String |
|
Categories of logging information to write to
The |
|
String |
|
Possible values mirror those listed on the
|
|
String |
|
Identity string to be prefixed to all messages logged to |
|
Boolean |
|
Log broker process ID with message? |
|
Boolean |
|
Write messages to system console if they cannot be sent to |
|
String |
Local time zone |
Time zone for log time stamps Possible values are the same as those used by the method Examples:
|
|
Boolean |
|
Enable writing of metrics information to Logger? Does not affect the production of metrics messages (controlled by |
|
Integer |
|
Time interval, in seconds, at which to write metrics information to Logger Does not affect the time interval for production of metrics messages (controlled by A value of |
|
Boolean |
|
Enable production of metrics messages to metric topic destinations? If |
|
Integer |
|
Time interval, in seconds, at which to produce metrics messages to metric topic destinations |
|
Boolean |
|
Are metrics messages sent to metric topic destinations persistent? |
|
Integer |
|
Lifetime, in seconds, of metrics messages sent to metric topic destinations |
|
String |
System property |
Name of primary system owner |
|
String |
System property |
Contact information for primary system owner |
|
Integer |
None |
Number of defined roles |
|
String |
Broker instance name |
Name of defined role N (where N ranges from 0 to .count-1) Example: ...name0=Stocks JMS Server ...name1=JMS provider for appserver |
Footnote 1 Can be used with imqcmd
update
bkr
command
Footnote 2 Solaris platform only
Footnote 3 Used by JES Monitoring Framework
Table 17-14 lists the configuration properties related to broker clusters.
Table 17-14 Broker Properties for Cluster Configuration
Property | Type | Default Value | Description |
---|---|---|---|
String |
None |
URL of Examples:
|
|
|
String |
None |
Host name or IP address for If specified, overrides |
|
Integer |
|
Port number for A value of |
|
String |
|
Network transport protocol for For secure, encrypted message delivery between brokers, set this property to |
|
Boolean |
|
Is broker part of an enhanced (high-availability) cluster? |
Additional Properties for Conventional Clusters |
|||
String |
None |
List of broker addresses belonging to cluster The list consists of one or more addresses, separated by commas. Each address specifies the Port Mapper host name and Port Mapper port number of a broker in the cluster, in the form hostName Example:
Literal IP addresses as host names: You can use a literal IPv4 or IPv6 address as a host name. If you use a literal IPv6 address, its format must conform to RFC2732, Format for Literal IPv6 Addresses in URL's. Note: If set, this property is ignored (and a warning logged) for high-availability clusters; all brokers configured to use the cluster's shared persistent store are automatically recognized as members of the cluster. |
|
Boolean |
|
Specifies whether a conventional cluster uses a shared JDBC database store for the cluster configuration change record instead of using a master broker. Set to When set to |
|
String |
None |
Port Mapper host name and Port Mapper port number of host on which cluster's master broker (if any) is running. The value has the form hostName Example:
Literal IP addresses as host names: You can use a literal IPv4 or IPv6 address as a host name. If you use a literal IPv6 address, its format must conform to RFC2732, Format for Literal IPv6 Addresses in URL's. Note: enhanced clusters cannot have a master broker. If this property is set for a broker belonging to an enhanced cluster, the broker will log a warning message and ignore the property. |
|
|
Boolean |
|
Can the master broker for the cluster be changed dynamically; that is, without stopping all the brokers in the cluster? If set to If set to |
|
String |
None |
Name of database vendor for shared JDBC data store housing the cluster configuration change record:
|
|
String |
per Vendor |
Java class name of the JDBC driver, if needed, for connecting to database from vendor vendorName for shared JDBC data store housing the cluster configuration change record |
|
String |
None |
URL for connecting to existing database from vendor vendorName for shared JDBC data store housing the cluster configuration change record Applicable when a |
|
String |
None |
URL for creating new database from vendor vendorName for shared JDBC data store housing the cluster configuration change record Applicable for embedded databases, such as Java DB. |
|
String |
None |
URL for closing connection to database from vendor vendorName for shared JDBC data store housing the cluster configuration change record Applicable for some embedded databases, such as Java DB. |
|
String |
None, except for MySQL |
Vendor-specific options passed to database from vendor vendorName for shared JDBC data store housing the cluster configuration change record when creating the table schema For information about this property's use, see the default broker properties file, |
|
String |
None |
User name, if required, for connecting to database from vendor vendorName for shared JDBC data store housing the cluster configuration change record |
|
Boolean |
|
Does database from vendor vendorName for shared JDBC data store housing the cluster configuration change record require a password for broker access? If |
|
String |
None |
Password, if required, for connecting to database from vendor vendorName for shared JDBC data store housing the cluster configuration change record This property should only be specified in a password file, as described in Password Files. |
|
String |
None |
Optional vendor-specific property propName for the JDBC driver from vendor vendorName for shared JDBC data store housing the cluster configuration change record |
Additional Properties for Enhanced (High-Availability) Clusters |
|||
String |
None |
Cluster identifier Must be a unique alphanumeric string of no more than n-13 characters, where n is the maximum table name length allowed by the database. No two running clusters may have the same cluster identifier. This string is appended to the names of all database tables in the cluster's shared persistent store. Note: For brokers belonging to a high-availability cluster, this property is used in database table names in place of |
|
|
Integer |
300 |
Time in seconds a failed broker attempting to restart waits for an existing takeover activity (from the broker's initial failure) to complete before exiting its restart attempt |
|
String |
None |
Host name for heartbeat service If specified, overrides |
|
Integer |
|
Port number for heartbeat service A value of |
|
Integer |
2 |
Interval between heartbeats, in seconds |
|
Integer |
3 |
Number of missed heartbeat intervals after which to invoke monitor service |
|
Integer |
30 |
Interval, in seconds, at which to update monitor time stamp Note: Larger values for this property will reduce the frequency of database access and thus improve overall system performance, but at the cost of slower detection and takeover in the event of broker failure. |
|
Integer |
2 |
Number of missed monitor intervals after which to initiate broker takeover |
Footnote 1 Must have the same value for all brokers in a cluster.
Footnote 2 Can be used with the imqcmd update bkr
command.
Footnote 3 Can be specified independently for each broker in a cluster.
Footnote 4 Conventional clusters only
Footnote 5 Enhanced (high-availability) clusters only
Table 17-15 lists broker properties related to the bridge service manager. Table 17-16 lists broker properties related specifically to the JMS bridge service, and Table 17-17 lists broker properties related specifically to the STOMP bridge service.
Table 17-15 Broker Properties for the Bridge Service Manager
Property | Type | Default Value | Description |
---|---|---|---|
|
Boolean |
|
Is the bridge service enabled on this broker? |
|
String |
None |
List of bridges that will be loaded on broker startup. The list consists of one or more bridge names, separated by commas. All bridge names for a broker must be unique. |
|
String |
None |
The Message Queue broker administrative user to be used by the bridge service manager and individual bridges to create ADMIN connections to the broker. For JMS bridges, this user is also used to access the JMS bridge's built-in DMQ destination. |
|
String |
None |
The password for the |
Table 17-16 Broker Properties for a JMS Bridge Service
Property | Type | Default Value | Description |
---|---|---|---|
|
String |
None |
The bridge type of the bridge named name. For JMS bridges, specify a value of |
|
String |
None |
The URL where the XML configuration file for the JMS bridge name is stored. Examples:
|
|
Boolean |
|
Should the JMS bridge name be automatically started when the broker is started? |
|
Integer |
|
The approximate maximum number of bytes the JMS bridge name writes to any one log file. A value of |
|
Integer |
|
The number of log files the JMS bridge name cycles through. |
|
String |
None |
Each of these properties specifies a list of key-value pairs for the built-in transaction coordinator for the JMS bridge name. The list consists of one or more key When the If the same key appears in both properties, the value specified in |
Table 17-17 Broker Properties for the STOMP Bridge Service
Property | Type | Default Value | Description |
---|---|---|---|
|
String |
None |
Host name or IP address for the STOMP bridge service If specified, overrides |
|
Boolean |
|
Does the STOMP bridge accept TCP connections? |
|
Integer |
|
The port on which the STOMP bridge listens for TCP connections, provided that |
|
Boolean |
|
Does the STOMP bridge accept SSL/TLS connections? If |
|
Integer |
|
The port on which the STOMP bridge listens for SSL/TLS connections, provided that |
|
Boolean |
|
Do SSL/TLS connections require client authentication? |
|
Integer |
|
The maximum number of unacknowledged messages that the STOMP bridge will deliver on a transacted STOMP subscription. The STOMP client must then acknowledge the messages and commit the transaction. |
|
String |
None |
The fully qualified class name of a class that extends the Message Queue bridge |
|
Integer |
|
The approximate maximum number of bytes the STOMP bridge writes to any one log file. A value of |
|
Integer |
|
The number of log files the STOMP bridge cycles through. |
The broker properties listed in Table 17-18 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 16-1.
See JMX Support for further information on administrative support of JMX clients.
Table 17-18 Broker Properties for JMX Support
Property | Type | Default Value | Description |
---|---|---|---|
|
String |
|
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 |
|
Use Secure Socket Layer (SSL) for connector connectorName? This property is set to |
|
Boolean |
|
Trust any certificate presented by broker for connector connectorName? Applies only when If If |
|
Boolean |
|
Start RMI registry at broker startup? If For convenience, this property can also be set at broker startup with the |
|
Boolean |
|
Use an existing RMI registry? Applies only if If For convenience, this property can also be set at broker startup with the |
|
Integer |
|
Port number of RMI registry Applies only if 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 |
Alphabetical List of Broker Properties is an alphabetical list of broker configuration properties, with cross-references to the relevant tables in this chapter.
Table 17-19 Alphabetical List of Broker Properties
Property | Table |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|