How to Trace MDB Listener
MDB Listener is consuming the data from the JMS Queue and it is not processing.
How can we trace MDB Listener.
Below process is not working
com.pega.pegarules.integration.engine.internal.services.jms.JMSListener
The above logger is not available to debug and to write in logs.
***Updated by moderator: Lochan to update Categories***
Accepted Solution
Pegasystems Inc.
IN
You will be already having PEGA as Appender in prlogging.xml you need to create one category for each class and add the class name
i.e
<category name="com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener" additivity="false">
<priority value="DEBUG"/>
<appender-ref ref="PEGA"/>
</category>
will fire debug logs and the MDBListener behaviour with the listener name.
from here you trace whether message is processed or not if you see any exceptions better raise SR for further investigation.
BUPA
AU
Hi,
JMS MDB Listeners are container managed and hence they don't come under normal tracer. Instead what you can do is to add log messages in your listener activity to trace the steps and output.
BUPA
AU
Hi ,
Did you try to put the sample message through Pega JMS explorer to check the underlying issue? Also check whether endpoints are running or not through your application server (Websphere/JBOSS etc) admin portal.
OCBC
IN
Hi,
I tried by adding a message through JMS explorer, from the queue message will be read but it is not processing, seems like Service JMS is not invoking from the Listener.
Pegasystems Inc.
IN
Please Add the loggers in debug mode for below classes in prlogging.xml it will pile up detailed steps of the message processing and MDBListener status in PegaRULES log file.
com.pega.pegarules.internal.etier.mdb.PRJMSListenerBoot
and
com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener
as MDB is deployed a separate EJB componet we can't control from SMA and Tarcer.
add these loggers only prlogging.xml not in designer studio loglevel settings.
Still if you are not able to find and resolve the issue raise and SR.
Thanks,
Narasimha
OCBC
IN
Hi Narasimha,
There are two types of tags to add loggers in prlogging.xml, like <appender> and <category> tags.
In which tag we should add our classes please let me know.
Thanks,
Gowd
Accepted Solution
Pegasystems Inc.
IN
You will be already having PEGA as Appender in prlogging.xml you need to create one category for each class and add the class name
i.e
<category name="com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener" additivity="false">
<priority value="DEBUG"/>
<appender-ref ref="PEGA"/>
</category>
will fire debug logs and the MDBListener behaviour with the listener name.
from here you trace whether message is processed or not if you see any exceptions better raise SR for further investigation.
Pegasystems Inc.
IN
Hello!
Please let us know if you do log an SR for this and its ID. That way we can track it and follow-up this discussion with the resolution.
Thank you,