JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server Message Queue 4.5 Administration Guide
search filter icon
search icon

Document Information


Part I Introduction to Message Queue Administration

1.  Administrative Tasks and Tools

2.  Quick-Start Tutorial

Part II Administrative Tasks

3.  Starting Brokers and Clients

4.  Configuring a Broker

5.  Managing a Broker

6.  Configuring and Managing Connection Services

7.  Managing Message Delivery

8.  Configuring Persistence Services

9.  Configuring and Managing Security Services

10.  Configuring and Managing Broker Clusters

11.  Managing Administered Objects

12.  Configuring and Managing Bridge Services

13.  Monitoring Broker Operations

14.  Analyzing and Tuning a Message Service

15.  Troubleshooting

Part III Reference

16.  Command Line Reference

17.  Broker Properties Reference

Connection Properties

Routing and Delivery Properties

Persistence Properties

File-Based Persistence Properties

File-Based Persistence Properties for Transaction Logging

JDBC-Based Persistence Properties

Security Properties

Monitoring Properties

Cluster Configuration Properties

Bridge Properties

JMX Properties

Alphabetical List of Broker Properties

18.  Physical Destination Property Reference

19.  Administered Object Attribute Reference

20.  JMS Resource Adapter Property Reference

21.  Metrics Information Reference

22.  JES Monitoring Framework Reference

Part IV Appendixes

A.  Distribution-Specific Locations of Message Queue Data

B.  Stability of Message Queue Interfaces

C.  HTTP/HTTPS Support

D.  JMX Support

E.  Frequently Used Command Utility Commands


Connection Properties

Table 17-1 lists the broker properties related to connection services.

Table 17-1 Broker Connection Properties

Default Value
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 (imq.cluster.ha = true), database table names also use the imq.cluster.clusterid property (see Table 17-14).

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.

All available IP addresses
Default host name or IP address for all connection services
Host name or IP address of Port Mapper

If specified, overrides imq.hostname. This might be necessary, for instance, if the broker’s host computer has more than one network interface card installed.

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.

Host name or IP address for connection service

If specified, overrides imq.hostname for the designated connection service. This might be necessary, for instance, if the broker’s host computer has more than one network interface card installed.

Port number for connection service

A value of 0 specifies that the port number should be allocated dynamically by the Port Mapper. You might need to set a different value, for instance, to specify a static port number for connecting to the broker through a firewall.

Maximum number of pending Port Mapper requests in operating system backlog
Threading model for thread pool management:
  • dedicated: Two dedicated threads per connection, one for incoming and one for outgoing messages

  • shared: Connections processed by shared thread when sending or receiving messages

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.
jms: 10ssljms: 10httpjms: 10 httpsjms: 10 admin: 4ssladmin: 4
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.

jms: 1000ssljms: 500httpjms: 500httpsjms : 500admin: 10ssladmin: 10
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 0 and greater than the value of imq.serviceName.min_threads.

The default value varies by connection service, as shown.

Solaris: 512Linux: 512Windows: 64
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 -1 denotes an unlimited number of connections per thread.

The default value varies by operating-system platform, as shown.
Interval, in seconds, at which to test connection between client and broker

A value of 0 or -1 disables periodic testing of the connection.

1Must have the same value for all brokers in an enhanced cluster.

2Can be used with imqcmd update bkr command

3jms, ssljms, admin, and ssladmin services only; see Appendix C, HTTP/HTTPS Support for information on configuring the httpjms and httpsjms services

4jms and admin services only

5Shared threading model only