MetaSolv Solution Work Order Integration Processing is Very Slow (Intermittent); Numerous BLOCKED Threads Waiting to Lock com.sun.jmx.interceptor.DefaultMBeanServerInterceptor Object
(Doc ID 1955982.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
*** Reviewed for relevance 03-MAY-2019 ***
The MetaSolv Solution Work Order integration processing intermittently works very slow. The WebLogic Admin and Managed servers are restarted and the Work Orders processing recovers and may slow down again. Thread dump evidence shows a thread contention problem where many ExecuteThreads are BLOCKED waiting to lock the com.sun.jmx.interceptor.DefaultMBeanServerInterceptor object.
THREAD DUMP INFO
The Thread Dump information below was taken over an 8 second period and evidence the thread contention pattern where ExecuteThreads for JMS messaging are waiting to lock the com.sun.jmx.interceptor.DefaultMBeanServerInterceptor object which is locked by another ExecuteThread. The example below shows ExecuteThread '150' waiting to lock the object to obtain channel configuration information from the Mbean, but it is BLOCKED by other ExecuteThreads ('142','13','137') over the period of time that obtain a lock on it for the same use.
Thread Dump 1 taken at YYYY-MM-DD 15:34:08
The issue cannot be reproduced at will.
The poor performance seriously impacts Work Order processing which causes delays in delivering services to customers.
The MetaSolv Solution work order integration load volume is high (JMS messages). The increased load volume may have been the result of higher than expected business activity or backlog due to communication problems between integrated systems (Example; SAF between MetasSolv Solution and OMS).
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