Siebel JMS Transport Unable to Reconnect After OC4J SOA Bounce
Last updated on MARCH 08, 2017
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.
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