WLS: SAF Messages Go Pending When WLS Endpoint Is Restarted - Source OSM and Destination UIM
(Doc ID 2184210.1)
Last updated on JANUARY 30, 2020
Applies to:Oracle WebLogic Server - Version 10.3.6 to 184.108.40.206.0
Information in this document applies to any platform.
A producer application was sending messages to a SAF configured for Uniform Distributed Destinations ( UDQ ). After some few messages were sent, messages started to pile up and go into pending status, making all related transactions to fail. The list of pending messages is observed on the console, and on the logs, below error message is observed:
Customer had the below settings in the source side but still doesn't work:
-Dweblogic.jms.saf.RefreshInterval=60(expressed in ms) -Dweblogic.SAFTXTimeout=250(expressed in seconds)
A value too low for weblogic.jms.saf.RefreshInterval could cause a LOT of problems as this value is in milliseconds. This means that the SAF will be continuously tearing down and recreating its connection. That value should be in the order of minutes instead.
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