My Oracle Support Banner

JMS queue showing Pending Messages on Newly Cloned Standalone OBDx Weblogic Server Not Receiving Any Frontend Request (Doc ID 2707907.1)

Last updated on SEPTEMBER 04, 2020

Applies to:

Oracle Banking Digital Experience - Version 17.1.0.0.0 to 20.1.0.0.0 [Release 11 to 20]
Information in this document applies to any platform.

Symptoms

 

ACTUAL BEHAVIOR 

---------------

Production environment consist of two independent WebLogic nodes hosting one Admin and OBDx managed server each.

 Both these nodes are not in cluster and are load balanced by frontend load balancer.

 Due to requirement of adding additional two WebLogic node existing VM was closed along with WebLogic domain .

 After due change in hostname / IP addresses on newly cloned instance WebLogic  Admin Server / OBDx managed server started without any problems.

 However on browsing to JMS queues there are many pending JMS messages seen on Queue even though this node is not receiving any traffic.

 

EXPECTED BEHAVIOR

-----------------------

Ideally Post Cloning , JMS queues should be empty to prevent duplicate processing of messages.

 

STEPS

-----------------------

This can be replicated by cloning existing Virtual machine with WebLogic  domain.

 

BUSINESS IMPACT

-----------------------

The issue has the following business impact:

Since JMS messages are still unprocessed on new instance , these messages may  get processed twice causing duplication.

Changes

 Existing Virtual machine hosting Weblogic domain was cloned along with local file system hosting JMS persistent store

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.