My Oracle Support Banner

Auto trigger functionality for swift messages is failing in TF (Doc ID 2733517.1)

Last updated on MARCH 23, 2021

Applies to:

Oracle Financial Services Transaction Filtering - Version 8.0.6 and later
Information in this document applies to any platform.

Symptoms

Swift error messages are not automatically re-posted once the EDQ servers are up and running and no messages are received with clean or hold status in JMS queue

Steps to reproduce : 

Step 1 : Stop the EDQ service like BIC out of 6 services in EDQ Director

Step 2 : Post the swift message

Step 3 : Restart the BIC service again after sometime

Step 4 : Check for the message posted earlier with help of group message id based on the interval time configured in SETUP_RT_PARAMS table or restart the webserver and check.

Expected result :

Alert must be created with retrigger id.

Actual result :

Auto trigger functionality does not work and alert is not created.

Issue screenshot : 

Changes

Load balancer has configured in spring-postsacalert.properties

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!


In this Document
Symptoms
Changes
Cause
Solution


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