For Weblogic 12.1.2 and below, FCDB Deployments in Warning Status when one of the Managed Servers is down and the Filestore is Targeted to same Managed Server where Cluster Targetting is not Supported
(Doc ID 2245825.1)
Last updated on JUNE 21, 2022
Applies to:Oracle FLEXCUBE Direct Banking - Version DB 6.0.1 to DB 12.0.3 [Release DB 6 to DB 12]
Information in this document applies to any platform.
On : FCDB versions 12.0.1/12.0.2/12.0.3 deployed in Weblogic versions 12.1.2 and below:
Some of the deployments like BulkEventHandlerEJB, ClonedQueueReceiverMDB which are responsible for Listening on the Queues and Processing those Messages which are posted on these Queues are in Warning State.
In case of a Cluster Configuration where there are two Managed Servers Managed_Server_1 & Managed_Server_2 are mapped to the Cluster, and Managed Server 1 is down.
The cluster is not available as a target when a File-store is created for a JMS Server, instead it is only possible to map the individual servers as target. In this case the filestore/JMS Mapping is done to Managed_Server_1 only.
When the Managed_Server_2 is down, all the Deployments are OK and is unaffected because the filestore/JMS Mapping is done to Managed_Server_1 only.
This happens specifically in Weblogic Versions 12.1.2 and below.
Deployments in Warning Status when a Particular Managed Server is down and the same has been targeted to the filestore / JMS Server
The issue can be reproduced at will with the following steps:
1. In a Cluster Configuration the two managed servers - Managed_Server_1 & Managed_Server_2 are mapped to a cluster, however the cluster is not available as a target when a filestore is created for a JMS Server, instead it gives the individual servers only for target.
2. The Filestore is targeted to Managed_Server_1 only because there is no option to map to Cluster
3. Bring down the Managed_Server_1. Some MDB Deployments which are responsible for listening on the Queue show up in Warning State. When this Managed_Server_1 is up and Managed_Server_2 is down there is no Impact.
The issue has the following business impact:
Due to this issue, the MDBs which are responsible for Listening on Queues and Processing the Messages sent/received on Queue are Stopped. No messages are Processed as there is no MDB Listening on the Queue
No changes to Environment, Product, Account and Hardware triggers this Problem.
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