My Oracle Support Banner

EDQ - Real Time Screening - Case Management Job Getting Stuck Due to MQ Issue and Does Not Fail (Doc ID 2921366.1)

Last updated on DECEMBER 17, 2024

Applies to:

Oracle Enterprise Data Quality - Version 12.2.1.4.0 and later
Oracle Enterprise Data Quality on Marketplace - Version 2.0 and later
Information in this document applies to any platform.

Symptoms

In Oracle Enterprise Data Quality (EDQ) Real Time Screening, there are two applications:

  1. Stateless Application
  2. Case Management Application.


Stateless Application gets a Simple Object Access Protocol (SOAP) request to perform initial screening. The Stateless Application performs the screening and responds back with the matching outcome (i.e. Match and No Match). If there is a Match, then the data is written to IBM MQ by the Stateless Application. After which, another application, Case Management (CM), reads the data from IBM Message Queue (MQ) and creates alerts in Case Management.

Here we have jobs running continuously on Stateless and CM applications which process live requests. If there is any issue with the MQ connection then the expectation is that the job should fail.

Previously, a fix was made where the job fails on the stateless server if there is any issue with the MQ connection.  A similar solution was implemented on the CM application, but it has been observed that the job is not failing as expected.  It appears to be stuck and does not complete or fail.  As a result, alerts are not created on the CM application.


Changes

 None

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.