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

Preface

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

Index

Bridge Properties

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
imq.bridge.enabled
Boolean
false
Is the bridge service enabled on this broker?
imq.bridge.activelist
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.

imq.bridge.admin.user
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.
imq.bridge.admin.password
String
None
The password for the imq.bridge.admin.user user.

Table 17-16 Broker Properties for a JMS Bridge Service

Property
Type
Default Value
Description
imq.bridge.name.type
String
None
The bridge type of the bridge named name. For JMS bridges, specify a value of JMS or jms.
imq.bridge.name.xmlurl
String
None
The URL where the XML configuration file for the JMS bridge name is stored.

Examples:

  • http://webserver/imq/jmsbridge1.config.xml

  • (for a file on a Web server)

  • file:/net/fileserver/imq/jmsbridge1.config.xml

  • (for a file on a shared drive)

imq.bridge.name.autostart
Boolean
true
Should the JMS bridge name be automatically started when the broker is started?
imq.bridge.name.logfile.limit
Integer
0
The approximate maximum number of bytes the JMS bridge name writes to any one log file.

A value of 0 (zero) indicates that there is no maximum limit.

imq.bridge.name.logfile.count
Integer
1
The number of log files the JMS bridge name cycles through.
imq.bridge.tm.props

imq.bridge.name.tm.props

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=value pairs separated by commas.

When the imq.persist.store is file, the built-in transaction coordinator supports these keys: txlogSize, txlogSync, and txlogMmap.

If the same key appears in both properties, the value specified in imq.bridge.name.tm.props takes precedence.

Table 17-17 Broker Properties for the STOMP Bridge Service

Property
Type
Default Value
Description
imq.bridge.stomp.hostname
String
None
Host name or IP address for the STOMP bridge service

If specified, overrides imq.hostname (see Table 17-1) for the STOMP bridge service.

imq.bridge.stomp.tcp.enabled
Boolean
true
Does the STOMP bridge accept TCP connections?
imq.bridge.stomp.tcp.port
Integer
7672
The port on which the STOMP bridge listens for TCP connections, provided that imq.bridge.stomp.tcp.enabled is true.
imq.bridge.stomp.tls.enabled
Boolean
false
Does the STOMP bridge accept SSL/TLS connections?

If true, a keystore must be created using the imqkeytool utility before starting the broker.

imq.bridge.stomp.tls.port
Integer
7673
The port on which the STOMP bridge listens for SSL/TLS connections, provided that imq.bridge.stomp.tls.enabled is true.
imq.bridge.stomp.tls.requireClientAuth
Boolean
false
Do SSL/TLS connections require client authentication?
imq.bridge.stomp.consumerFlowLimit
Integer
1000
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.
imq.bridge.stomp.messageTransformer
String
None
The fully qualified class name of a class that extends the Message Queue bridge MessageTransformer abstract class by implementing the transform() method. Place this class under the IMQ_HOME/lib/ext. directory
imq.bridge.stomp.logfile.limit
Integer
0
The approximate maximum number of bytes the STOMP bridge writes to any one log file.

A value of 0 (zero) indicates that there is no maximum limit.

imq.bridge.stomp.logfile.count
Integer
1
The number of log files the STOMP bridge cycles through.