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

18.  Physical Destination Property Reference

19.  Administered Object Attribute Reference

20.  JMS Resource Adapter Property Reference

About Shared Topic Subscriptions for Clustered Containers

Disabling Shared Subscriptions

Consumer Flow Control When Shared Subscriptions Are Used

ResourceAdapter JavaBean

ManagedConnectionFactory JavaBean

ActivationSpec JavaBean

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

ResourceAdapter JavaBean

The ResourceAdapter configuration configures the default JMS Resource Adapter behavior. Table 20-1 lists and describes the properties with which you can configure this JavaBean.

Table 20-1 Resource Adapter Properties

Property
Type
Default Value
Description
connectionURL1
String
mq://localhost:7676/jms
Message service address for connecting to the Message Queue service
brokerInstanceName
String
imqbroker
Name of broker instance
brokerPort
Integer
7676
Port number for connecting to broker
brokerBindAddress
String
Null
Address to which broker binds on host machine

If null, the broker will bind to all addresses on the host machine.

userName2
String
guest
Default user name for connecting to Message Queue service
password2
String
guest
Default password for connecting to Message Queue service
addressListBehavior
String
PRIORITY
Order in which to attempt connection to Message Queue service:
  • PRIORITY: Order specified in address list

  • RANDOM: Random order


Note - Reconnection attempts after a connection failure start with the broker whose connection failed and proceed sequentially through the address list, regardless of the value set for this property.


addressListIterations
Integer
1
Number of times to iterate through address list attempting to establish or reestablish a connection
reconnectEnabled
Boolean
false
Attempt to reestablish a lost connection?
reconnectAttempts
Integer
6
Number of times to attempt reconnection to each address in address list before moving on to next
reconnectInterval
Long integer
30000
Interval, in milliseconds, between reconnection attempts
brokerEnableHA
Boolean
false
Enable high availability?
clusterID
String
None
Cluster identifier

If specified, only brokers with the same cluster identifier can be clustered together. In the event of broker failure, client connections will fail over only to brokers with the same cluster identifier as the original broker. If not specified, client connections can fail over to any other broker with an unspecified cluster identifier.

For standalone brokers (those not belonging to a cluster), this property is ignored.

The identifier may contain only alphabetic letters (AZ, az), numeric digits (09), and the underscore character (_).

brokerID
String
None
Broker identifier

For brokers using a JDBC-based persistent data store, this string is appended to the names of all database tables to make them unique in the case where more than one broker instance is using the same database. For brokers using a file-based data store, this property is ignored.

In an enhanced cluster, each broker must have a unique broker identifier.

The identifier may contain only alphabetic letters (AZ, az), numeric digits (09), and the underscore character (_).

1Must be specified

2Required