Support Article

JMS Listener processing too quickly upon server startup

SA-26132

Summary



​If there are items in a JMS queue, upon server restart the JMS Listener will not be able to process them and cause NullpointerException.


Error Messages



2016-06-11 18:25:12,720 [ JMS-Thread-39] [ STANDARD] [an_app:04.20.01] ( internal.access.DatabaseImpl) ERROR .a_Process|JMS|a_JMS|ServiceJMS|createProcess|A38AFAB57E05953A79A7FC9AF90A494B0 ppe_service - Encountered p 
roblem when performing a Commit 
java.lang.NullPointerException 
at com.pega.pegarules.session.internal.mgmt.base.RequestorChildren.queueBatchActivity(RequestorChildren.java:216) 
at com.pega.pegarules.session.internal.mgmt.base.RequestorChildren.queueBatchActivity(RequestorChildren.java:174) 
at com.pega.pegarules.session.internal.mgmt.PRRequestorImpl.queueBatchActivity(PRRequestorImpl.java:1125) 
at com.pega.pegarules.exec.internal.declare.infengine.ChainingEngineUtilImpl.runActivity(ChainingEngineUtilImpl.java:283) 
at com.pega.pegarules.exec.internal.declare.infengine.TriggerImpl.evaluateNetworks(TriggerImpl.java:307) 
at com.pega.pegarules.data.internal.access.DatabaseImpl.performTriggers(DatabaseImpl.java:12805) 
at com.pega.pegarules.data.internal.access.DatabaseImpl.performCommitTriggers(DatabaseImpl.java:2799) 
at com.pega.pegarules.data.internal.access.DatabaseImpl.attemptToProcessUpdates(DatabaseImpl.java:2609) 
at com.pega.pegarules.data.internal.access.DatabaseImpl.processUpdates(DatabaseImpl.java:2308) 


Steps to Reproduce



Restart the server while there are JMS messages in the queue.


Root Cause



A defect in Pegasystems’ code or rules

Resolution



Apply HFix-28560

 

Published July 28, 2016 - Updated July 31, 2016

Have a question? Get answers now.

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