A JMS MDB service is configured to consume incoming messages asynchronously though a service request processor rule. It is configured to use the out of the box SYSTEM-QUEUE-EXECUTIONREQUEST-SERVICE-DEFAULT and ProcessServiceQueue agent.

Messages remains stuck in the SYSTEM-QUEUE-EXECUTIONREQUEST-SERVICE-DEFAULT queue with 0 attempts from the agent and a InstanceNotFound exception is logged by the agent.

STEPS TO REPRODUCE

1. Configure a JMS MDB service to process messages asynchronously using a request processor rule from the default SYSTEM-QUEUE-EXECUTIONREQUEST-SERVICE-DEFAULT queue;
2. Put a message on the JMS queue and wait it is consumed by the Pega JMS MDB listener;
3. Open the SMA and display the SYSTEM-QUEUE-EXECUTIONREQUEST-SERVICE-DEFAULT queue: some messages remains stuck in the queue with 0 attempts.

Error Message :

2016-09-07 10:44:24,258 [fault (self-tuning)'](    async.agent.QueueProcessor) WARN    - Failed to dequeue item: SYSTEM-QUEUE-EXECUTIONREQUEST-SERVICE-DEFAULT 1473254199146000207DB72CC168D1FE17F1ABFF2C4561A0 for processing;com.pega.pegarules.pub.context.PRQueueException: InstanceNotFound    Queue    SYSTEM-QUEUE-EXECUTIONREQUEST-SERVICE-DEFAULT    SYSTEM-QUEUE-EXECUTIONREQUEST-SERVICE-DEFAULT 1473254199146000207DB72CC168D1FE17F1ABFF2C4561A0;    at com.pega.pegarules.session.internal.async.agent.QueueManagerImpl.dequeue(QueueManagerImpl.java:720);    at com.pega.pegarules.session.internal.async.agent.QueueManagerImpl.dequeue(QueueManagerImpl.java:635);    at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:372);    at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:801);    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1032);    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:733);    at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:556);    at com.pega.pegarules.session.internal.engineinterface.service.RequestProcessorImpl.processServiceRequest(RequestProcessorImpl.java:735);    at com.pega.pegarules.session.internal.engineinterface.service.RequestProcessorImpl.processQueue(RequestProcessorImpl.java:636);    at com.pegarules.generated.activity.ra_action_processqueue_220a7c569860841f205ded64d7e39ca5.step1_circum0(ra_action_processqueue_220a7c569860841f205ded64d7e39ca5.java:182);

***Updated by Moderator: Vidyaranjan. Removed user added  Ask the Expert tag. Apologies for confusion, shouldn't have been an end-user option*** Included categories***