New RIB Installation: "Could Not Get Status of the JMS Server" Error Upon Starting JMS
(Doc ID 1316328.1)
Last updated on MARCH 14, 2019
Applies to:Oracle Retail Integration Bus - Version 11.0 to 12.0.11 [Release 11 to 12.0]
Information in this document applies to any platform.
For a new Installation of Retail Integration Bus (RIB), when attempting to start the Java Messaging Service (JMS) for the first time using "start_rib JMS" command, the script returns the following error:
Also, in the Schema Designer, the Control Broker entry is located within a Participating Host which is marked as "inactive".
In some cases, messages like the following appear in the log file for the registry (stcregd.log), and point to issues with the registry and the participating host install:
21:27:33.193 REG D 30 (connectionmain.cxx:92): client command failed: [rFND]
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