My Oracle Support Banner

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

Last updated on OCTOBER 15, 2020

Applies to:

Oracle Containers for J2EE - Version 10.1.3.3.0 and later
Information in this document applies to any platform.
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

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
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.