Because the JMS service configuration is part of the overall configuration for a standalone instance or cluster, it is created when the standalone instance or cluster is created. You can then update the JMS service configuration by using the Java Message Service page for the configuration in the Administration Console, or by using a set subcommand of the following form:
The attributes you can set are:
The JMS host type the service is to use. Available choices are EMBEDDED, LOCAL and REMOTE. See About JMS Host Types for more information.
The number of seconds GlassFish Server waits for the JMS service to start before aborting the startup.
A list of arguments the JMS service passes to Embedded and Local type JMS hosts on startup. Permissible arguments are the options supported by the Message Queue imqbrokerd command, as described in Broker Utility in Oracle GlassFish Server Message Queue 4.5 Administration Guide.
The name of the default JMS host.
When set to true, the JMS service attempts to reconnect to a JMS host (or one of the JMS hosts in the AddressList) when a connection is lost.
The number of attempts to connect (or reconnect) for each JMS host in the AddressList before the JMS service tries the next address in the list. A value of -1 indicates that the number of reconnect attempts is unlimited (the JMS service attempts to connect to the first address until it succeeds).
The number of seconds between reconnect attempts. This interval applies for attempts on each JMS host in the AddressList and for successive addresses in the list. If it is too short, this time interval does not give a JMS host time to recover. If it is too long, the reconnect might represent an unacceptable delay.
The order of connection attempts. Available choices are:
Select a JMS host from the AddressList randomly. If there are many clients attempting a connection using the same connection factory, specify random to prevent them from all being connected to the same JMS host.
Always try to connect to the first JMS host in the AddressList and use another one only if the first one is not available.
The number of times the JMS service iterates through the AddressList in an effort to establish (or reestablish) a connection. A value of -1 indicates that the number of attempts is unlimited.
The Message Queue address scheme name and connection service name to use for the AddressList if a non-default scheme or service is to be used. See Connection Handling in Oracle GlassFish Server Message Queue 4.5 Administration Guide for syntax information.
Note - After making changes to the JMS service configuration, GlassFish Server instances that use the configuration must be restarted in order for the changes to be propagated.
You can specify any Message Queue broker property in the JMS service configuration by adding it by name to the Additional Properties table on the Java Message Service page for the configuration in the Administration Console, or by using a set subcommand of the following form:
If the broker property name includes dots, preface the dots with two backslashes (\\); for example, to set the imq.system.max_count property, specify imq\\.system\\.max_count in the set subcommand.
Note - You can also set broker properties in the JMS host. If you set the same broker property in both the JMS service configuration and the JMS host, the value specified in the JMS host is used.