Siebel JMS Transport Unable to Reconnect After OC4J SOA Bounce (Doc ID 832733.1)

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.

Symptoms

Siebel 8.0.0.2 JMS Transport is not able to reconnect after a JMS Server (OC4J SOA Suite 10.1.3.3) bounce. Using the OC4J JMS provider in the SOA Suite.

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.

Cause

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