Siebel JMS Transport Unable to Reconnect After OC4J SOA Bounce
(Doc ID 832733.1)
Last updated on AUGUST 10, 2018
Applies to:Oracle Containers for J2EE - Version: 10.1.3.3.0
This problem can occur on any platform.
The error message is :
Exception: javax.jms.JMSException: [INTERNAL ERROR] JMSRemoteServer[Oracle Containers for J2EE 10g (10.1.3.3.0) (build "070610.1800.23513")]: is not yet registered.;
which is coming from the JMS server and not Siebel.
If OC4J SOA suite(JMSServer) is bounced, JMS transport components in Siebel need to be restarted.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.|