Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

JMS MDB listener processes events late

SA-75282

Summary



Java Messaging  Service (JMS) Message-Driven Bean (MDB) Listener's performance degrades when processing events.


Error Messages



[CDCN:Administrators]] [STANDARD] [ ] [PMCDCN:01.01.01] (tor$QueueBasedDataFlowExecutor) ERROR JMS|HSBCFWPMCDDataCardTxn|Services|ProcessCardTxn|A30913CADA0ADFEDEF477087FE145969A  - Unable to queue record for 5 minutes for processing in data flow. Retrying.
[CDCN:Administrators]] [STANDARD] [ ] [PMCDCN:01.01.01] (tor$QueueBasedDataFlowExecutor) ERROR JMS|HSBCFWPMCDDataCardTxn|Services|ProcessCardTxn|A30913CADA0ADFEDEF477087FE145969A  - Unable to queue record for 5 minutes for processing in data flow. Retrying.

PEGA005 alert in the logs processing the JMS transactions.



Steps to Reproduce



Unknown


Root Cause



The JMS listener processed the data from the MDB queue and saved it in a database.


Resolution



Here's the explanation for the reported behavior:

Obj-Save was used which caused the events to be processed late.

As a local-change, use the DataFlow-Execute method to save data.

Published August 15, 2019 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us