Thread contention observed on "weblogic.jms.common.CDSRemoteProxy" during network disruption with SAF (for forwarding messages)
(Doc ID 1606368.1)
Last updated on AUGUST 14, 2020
Applies to:Oracle WebLogic Server - Version 10.3.4 to 18.104.22.168.0
Information in this document applies to any platform.
A JMS Application sends a message to Oracle Service Bus (OSB), the OSB puts this message on WebLogic Server Store-And-Forward (WLS SAF). This application waits for 10 seconds to receive the response (which is the business requirement). The response time here is calculated from OSB to SAF (irrespective wether the SAF forwarder is forwarding or not).
The IP addresses of the SAF remote context is unplumbed (removing the mapping of the ip address) in order to disrupt the network connectivity.
This is because it was observed that, in case of a network disconnectivity (may be due to network hardware failure), then, for few minutes, the SAF implementation faces an issue with thread contention leading to a message pile-up and unexpected increase in time (which is calculated based on load runs) during forwarder call, as the SAF implementation tries to look-up remote context (which is not available during the network disconnection) for forwarding messages.
Everything becomes normal as SAF forwards after a certain time (that varies from few seconds to few minutes) automatically.
The primary concern being the window during the network disconnection, and the technical cause for the same.
How to verify the issue:
Here, response time was calculated by the time-taken on Extended Logging Format Fields and change the Format from Common to Extended.
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