Siebel JMS Transport Unable to Reconnect After OC4J SOA Bounce
(Doc ID 832733.1)
Last updated on OCTOBER 26, 2021
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.
Siebel 188.8.131.52 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 :
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