Question

6
Replies
700
Views
RajasekharU0829 Member since 2013 98 posts
Techmahindra
Posted: 5 years ago
Last activity: 5 years 4 months ago
Closed
Solved

JMS MDB Listener: Missing Inbound messages

We got missing message in SI because the application doesn’t handle exception during message processing.

please help in identifying the root cause and solution for below issue

2015-05-15 11:23:19,096 [20550502962094AF01]]] [ STANDARD]
[
] ( internal.mgmt.RequestorPool) ERROR
JMS|ScotiaJMS|Scotia-GWS-Work-MsgCase|ScotiaJMSService - Timed out
borrowing service requestor from requestor pool

2015-05-15 11:23:19,104 [20550502962094AF01]]] [ STANDARD]
[
] (
internal.mgmt.PREnvironment) ERROR
JMS|ScotiaJMS|Scotia-GWS-Work-MsgCase|ScotiaJMSService - Problem
obtaining requestor from ServiceRequestorPool

  1. com.pega.pegarules.pub.PRException: Timed out borrowing service
    requestor from requestor pool

From: (unknown)
at
com.pega.pegarules.session.internal.mgmt.RequestorPool.borrowRequestor(RequestorPool.java:464)

at
com.pega.pegarules.session.internal.mgmt.RequestorPoolManager.borrowRequestor(RequestorPoolManager.java:61)

at com.pega.pegarules.session.internal.PRSessionProviderImpl.borrowRequestor(PRSessionProviderImpl.java:569)

at
com.pega.pegarules.session.external.engineinterface.service.EngineAPI.establishRequestor(EngineAPI.java:734)

at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.findRequestor(ServiceAPI.java:1138)

at
com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:327)

at
com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.handleRequest(JMSListener.java:1245)

at
com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.runOnce(JMSListener.java:691)

at java.lang.reflect.Method.invoke(Method.java:597)

………………………………………………………..
at
weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:486)

at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:388)

at
com.ibm.mq.jms.MQMessageConsumer$FacadeMessageListener.onMessage(MQMessageConsumer.java:336)

at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl$JmsProviderMessageListener.onMessage(JmsMessageConsumerImpl.java:928)

at
com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.honourNoLocal(WMQAsyncConsumerShadow.java:636)

at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.consumer(WMQAsyncConsumerShadow.java:473)

at
com.ibm.mq.jmqi.remote.impl.RemoteProxyQueue.driveConsumer(RemoteProxyQueue.java:4297)

at
com.ibm.mq.jmqi.remote.impl.RemoteProxyQueue.deliverMsgs(RemoteProxyQueue.java:4882)

at
com.ibm.mq.jmqi.remote.impl.RemoteDispatchThread.deliverMsgsReconnectable(RemoteDispatchThread.java:541)

at
com.ibm.mq.jmqi.remote.impl.RemoteDispatchThread.deliverMsgs(RemoteDispatchThread.java:513)

at
com.ibm.mq.jmqi.remote.impl.RemoteDispatchThread.run(RemoteDispatchThread.java:282)

at
com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.runTask(WorkQueueItem.java:214)

at com.ibm.msg.client.commonservices.workqueue.SimpleWorkQueueItem.runItem(SimpleWorkQueueItem.java:105)

at
com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.run(WorkQueueItem.java:229)

at com.ibm.msg.client.commonservices.workqueue.WorkQueueManager.runWorkQueueItem(WorkQueueManager.java:303)

at
com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation$ThreadPoolWorker.run(WorkQueueManagerImplementation.java:1219)

Caused by: java.util.NoSuchElementException: Timeout waiting for idle object
at
com.pega.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:751)

at
com.pega.pegarules.session.internal.mgmt.RequestorPool.borrowRequestor(RequestorPool.java:455)

... 47 more

***Updated by moderator: Marissa to close post***

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Data Integration
Moderation Team has archived post
Share this page LinkedIn