How to Determine the Message that SFM Event Manager is Trying to Process
(Doc ID 358623.1)
Last updated on OCTOBER 08, 2018
Applies to:Oracle Installed Base - Version 11.5.9 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
Oracle Service Fulfillment Manager (a/k/a SFM, SDP, Provisioning) is a highly performing and scalable order fulfillment system that supports distributed customizable business processes, interfaces with legacy systems, and utilizes messaging. SFM provides and uses highly performing, multi-threaded Queue Services to process its transactions.
Sometimes SFM is up and running as normal, but is not processing any messages (or so it seems); The number of messages with msg_status = 'PROCESSED' in the xnp_msgs table is not increasing. This behavior usually means SFM is trying to process a message but gets 'stuck' on it. It is going into an endless loop or waiting for locks to be released. When picking up a message to process, SFM uses the processing logic of the message type to determine what APIs to execute. In cases where SFM gets stuck on processing, the processing logic usually causes the problem.
The trick is to identify what message SFM is currently trying to process. This document intends to assist in that task. After identifying the message, investigation needs to continue to find why it is causing SFM to get stuck. The notes referenced below may be of assistance in that continued research.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|