SAF Agent Not Sending Messages on the Remote Server When the Admin Port is Enabled on the SAF Agent
(Doc ID 2319964.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle WebLogic Server - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Oracle WebLogic Server 220.127.116.11.0 is set up for Store-and-Forward (SAF) service with:
SOURCE: OSB 12c with WLS 12.2.1.x.x
TARGET: SOA 11g with WLS 10.3.6.0.x
The problem is that the SAF Agent is NOT sending messages on the remote server when the Admin Port is enabled on the SAF Agent WLS 12c instance (source).
OSB 12.2.1 is unable to connect to JMS Destination when AdminPort and SSL Listen Ports are active.
This integration has an SAF agent configured with OSB 12c which connects to a JMS Queue in the SOA 11g side. This works fine.
When OSB 12c AdminPort and SSL Listen Ports are enabled in the OSB Cluster/domain, the integration between OSB 12c <> SOA 11g hits multiple errors and many open sockets.
Log entries are complaining about not finding the remote connection factory, "unable to connect to the JMS destination".
This combination is as a result of recently upgrading OSB to 12c.
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