Detecting Slow Consumer On Distributed Topic Using WLS MBEANS
(Doc ID 1481133.1)
Last updated on AUGUST 22, 2022
Applies to:Oracle WebLogic Server - Version 10.3.5 and later
Information in this document applies to any platform.
In case your consumers, for a Distributed Topic (DT), are slow and due to that slowness, the durable messages for such slow consumers may start accumulating in the memory and may cause the memory to choked up for longer time or may also lead to OutOfMemory situation.
In such case, if you wanted to identify the particular slow consumers and if there are large number of consumers listening on that DT, it is tough to identify any particular consumer which is actually slow.
This can be tracked using the debug flags JMS message path, Frontend and backend but in case the issue is happening in a critical environment where the debugs cannot be enabled that would add more difficulty.
At the moment, there is no runtime Mbean for non-durable subscriptions which can be used to Monitor the non-durable distributed topics consumers status/backlog and other statistics.
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