Unexpected High CPU Utilization when JMS Clients are Connected to WebLogic JMS Queue
(Doc ID 2709773.1)
Last updated on SEPTEMBER 16, 2020
Applies to:Oracle WebLogic Server - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Unexpected CPU utilization of 20-30% is noted when JMS clients are connected to WebLogic JMS Queues.
WLS domain has JMS queues to which JMS clients, connect over t3 connection. A steady CPU usage was noted even when there are no messages to be consumed from the JMS queue and when 10 parallel JMS clients were running.
If the JMS clients are stopped the CPU goes down to under 5%.
High CPU threads from top and threaddump coorelation shows below muxer threads using 10% CPU each.
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