When the JMS Broker is Down, Oracle Enterprise Gateway Policy Studio Cannot Deploy Policies Which Configure a JMS Service (Doc ID 1579108.1)

Last updated on AUGUST 18, 2016

Applies to:

Oracle API Gateway - Version to [Release 11gR1]
Information in this document applies to any platform.


Using Oracle Enterprise Gateway

A JMS service is configured, for example with IBM Websphere or WebLogic, as the JMS broker.

The patch for <Bug 13798494> - OEG DOES NOT START WHEN WEBSPHERE MQ IS UNAVAILABLE is applied.


An example of the error messages shown from Policy Studio when WebLogic is used as the JMS broker is as follows:


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