Message Queue Broker Modes

Message Queue can be integrated with GlassFish Server in LOCAL, REMOTE, or EMBEDDED mode. These modes are represented by the JMS type attribute.

• LOCAL Mode. GlassFish Server starts and stops the Message Queue broker that is specified as the default JMS host. The Message Queue process is started in a separate virtual machine from the GlassFish Server process. GlassFish Server supplies an additional port to the broker, which is used by the broker to start the RMI registry. This port number will be equal to the configured JMS port for that instance, plus 100. For example, if the JMS port number is 37676, then this additional port number is 37776.

  In LOCAL mode, use the Start Arguments attribute to specify Message Queue broker startup parameters.

• REMOTE Mode. When the type attribute is set to REMOTE, the Message Queue broker must be started and stopped separately from GlassFish Server. Message Queue tools must be used to configure and tune the broker. In this situation, GlassFish Server uses an externally–configured broker or broker cluster. REMOTE type is most suitable for clusters.

  In REMOTE mode, you must specify Message Queue broker startup parameters using Message Queue tools. The Start Arguments attribute is ignored.

• EMBEDDED Mode (default). When the JMS type attribute is set to EMBEDDED, GlassFish Server and the JMS broker are colocated in the same virtual machine. The JMS Service is started in-process and managed by GlassFish Server.

  In EMBEDDED mode, the JMS operations bypass the networking stack, which leads to performance optimization.

For information about administering Message Queue, see Oracle GlassFish Message Queue 4.4.2 Administration Guide.