WebLogic Console Slowness Related to com.bea.console.utils.DeploymentUtils.haveUnactivatedChanges
(Doc ID 2805573.1)
Last updated on APRIL 29, 2022
Applies to:Oracle WebLogic Server - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
WebLogic console takes 10-15 seconds to return the status page with the server's summary. A consistent 5-seconds slowness is seen in other pages as well, for example, monitoring under the AdminServer.
Following <Note 2574782.1>: Troubleshooting WLS Performance Issues With JFR
a 1-minute JFR was collected setting the thread dump interval to 5 seconds and including some attempts to access different pages of the console under AdminServer > Monitoring.
The JFR file was analyzed with JMC 8 that can be download from https://www.oracle.com/java/technologies/javase/products-jmc8-downloads.html
Steps to troubleshoot:
1- from WebLogic > Servlet Invocation by URI, clearly if the list of requests is ordered by duration, 9 requests taking around 5 seconds are seen, belonging to ExecuteThread 30, and ExecuteThread 37:
With that set of 9 requests a 1st stored selection was created to group the events related. Stored selections can be accessed by every view in JCM8 from Focus/Aspect.
3- from Java Application > Thread Dumps, 10 thread dumps were captured during this 1-minute sample (1 thread dump every 5 seconds), thus it's highly probable that one of these 9 requests matched with these 10 thread dumps.
2- from Java Application > Threads > (Legacy) Threads, the new stored selection was selected from Focus/Aspects, showing graphically these slow requests.
One of these requests corresponding to ExecuteThread 37 is selected to create a 2nd stored selection.
3- When checking if the 2nd stored selection matched with one of the 10 thread dumps, it matched with the one collected at 9:38:51:
If searching for ACTIVE threads, specifically ExecuteThread 37, the stack trace was captured:
4- to double check this finding the same exercise was performed for a second slow request corresponding to ExecuteThread 30, getting to a similar stack trace:
However, there were no pending changes.
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