DM_FUSA Backend Reaches 100% CPU Utilization On A Verification Request And Never Returns
(Doc ID 2619631.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
The PaymenTech data manager (dm_fusa) is observed to increase to 100% CPU utilization, and does not return the validate transaction that it was currently working on. This in turn results in the master connection manager (CM) process connecting to this dm_fusa process to rise in child CM counts.
DM_FUSA backend reaches 100% CPU utilization on a verification request like below and never returns:
As a workaround, the dm_fusa and CM instances are isolated and traffic routed to redundant servers already in the pool. The affected instance is restarted.
Numbers of transactions accepted 107,669 and 107,319 transactions processed until the dm_fusa backend that was hung was killed, then the remaining accepted transactions were processed through.
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