My Oracle Support Banner

Occasional "Timed Out Exception" in OBDx When Installed on 2 Node Weblogic Cluster and Integrated With Third Party Host Through JMS (Doc ID 2745738.1)

Last updated on FEBRUARY 02, 2021

Applies to:

Oracle Banking Digital Experience - Version 18.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to use OBDx application on clustered environment and EXT System Sender and Receiver queues are created as distributed queues on the same cluster,
the following error occurs for some REST calls.

ERROR
-----------------------
com.ofss.digx.infra.exceptions.Exception: Timed out exception.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Configure a cluster of OBDx servers.
2. Create EXT System Sender and Receiver as distributed queues.
3. Login as retail user.
4. Observe some REST calls get Timed out exception.

BUSINESS IMPACT
-----------------------
Due to this issue, distributed queues cannot be used and due to this limitation, implementer uses non-distributed queues. In case of non-distributed queues, it is observed that bringing down one server in cluster is causing unavailability of queues even on the server which is in "Running" state.

Changes

 

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
References


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