We recently configured JMS MDB listener and it is getting stuck/disabled due to some exceptions( no errors in the pega logs). Usually middleware/SOA team monitors the corresponding Queues and sends notification if the queue is stuck with a number (threshold mentioned in their configuration) of messages but it my current client Pega should handle this. As per my understanding and knowledge there is no direct way of monitoring it unless you manually check it every day/time.
I don't see any way of configuring it in PRPC or AES, please let me know how to monitor JMS MDB listener either from PRPC(7.1.7) or AES(V3.5)
Thank you Rajiv, I have looked at this article before looks like we have to write some custom java code to monitor the Beans. Will try to explore this approach in AES as we have to monitor all pega application queue/listeners.
Posted: 6 years ago
Posted: 13 Nov 2015 0:40 EST
Rajiv Nistala (nistr)
Senior Manager - Engineering