JMS Messages Sent From OCECAS Application Are Getting Generated in Prod_Domain, But They Are Not Sent To Remote_Domain, But Sent To a JMS Temporary Queue
(Doc ID 2672258.1)
Last updated on MAY 20, 2020
Applies to:Oracle WebLogic Server - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 12c]
Information in this document applies to any platform.
The OCECAS application is a product based on Weblogic.
The JMS is a basic SAF configuration.
Store-and-Forward (SAF) is another mechanism WebLogic provides to transfer messages from one source to a target destination.
The WebLogic messaging bridge and the SAF work in a similar way although the SAF is recommended over the messaging bridge when used to transfer messages between domains with WebLogic Versions.
There are two domains : the Remote_Domain and Prod_Domain
The OCECAS application generates JMS messages (EDRS) in the Prod_Domain, but they are not sent to the Remote_Domain.
Once the JMS messages reach the Remote_Domain from Prod_Domain, they are written to a JMS temporary queue.
There have been noticed RJVM stuck threads.
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