My Oracle Support Banner

Configuring GlassFish Server to Start When a Message Queue Broker is Not Available (Doc ID 1297871.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle GlassFish Server - Version: 2.1 to 2.1.1 - Release: 2.1 to 2.1
Information in this document applies to any platform.

Goal

When starting a GlassFish Server instance, the instance always attempts to connect to the default Message Queue (MQ) broker in its configuration.  If, for some reason, the MQ broker is running and the GlassFish Server instance fails to connect to the MQ broker, then the instance will terminate its startup and exit.

The purpose of this document is to provide the steps to alter the configuration so that the connection to the MQ broker is performed lazily, so that the  instance will complete its startup, regardless of whether the MQ broker becomes available later, or if one is never started as the instance does not use any Java Message Service (JMS) functionality.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
  Goal
  Solution
  References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.