Configuring GlassFish Server to Start When a Message Queue Broker is Not Available
Last updated on NOVEMBER 05, 2016
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.
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms