Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 pradeep pydi (pradeepp2840)
Verizon Wireless
PEGA SENIOR SYSTEM ENGINEER
Verizon Wireless
US
pradeepp2840 Member since 2017 20 posts
Verizon Wireless
Posted: Jun 7, 2017
Last activity: Jul 11, 2017
Posted: 7 Jun 2017 11:30 EDT
Last activity: 11 Jul 2017 16:31 EDT
Closed
Solved

Issues with JMS MDB Listener

Hi Team,

The below mentioned JMS MDB Listener related error messages have been observed in the logs.

PEGA Version : 7.2.0

Show More

Hi Team,

The below mentioned JMS MDB Listener related error messages have been observed in the logs.

PEGA Version : 7.2.0

2017-06-06 15:36:09,886 [AResourceAdapter : 0] [ STANDARD] [ ] ( services.jms.JMSListener) ERROR - Caught exception while trying to send a response error message
com.pega.pegarules.pub.services.ServiceException: Caught exception while processing request for service VZWCSC.CM.InvokeDetailOrderNotifications, com.pega.pegarules.pub.PRException: Expecting a StreamMessage, received a message of type:
com.ibm.jms.JMSMapMessage
From: (unknown)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.handleException(JMSListener.java:1495)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.runOnce(JMSListener.java:712)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListenerServant.invoke(JMSListenerServant.java:112)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:327)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:270)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:411)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:224)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingException(AppServe
[6/6/17 15:36:37:651 EDT] 00000025 SibMessage W CWWMQ0007W: The message endpoint etr_ws#prbeans.jar#POSNotifications has been paused by the system. Message delivery failed to the endpoint more than 0 times. The last attempted delivery failed with the following error: com.ibm.ejs.container.UnknownLocalException: nested exception is: java.lang.RuntimeException: Problem during method invocation (onMessage)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:279)
at com.pega.pegarules.internal.etier.mdb.PRJMSListenerBoot.onMessage(PRJMSListenerBoot.java:91)
at com.ibm.ejs.container.MessageEndpointHandler.invokeMdbMethod(MessageEndpointHandler.java:1163)
at com.ibm.ejs.container.MessageEndpointHandler.invoke(MessageEndpointHandler.java:842)
at com.sun.proxy.$Proxy23.onMessage(Unknown Source)
at com.ibm.mq.connector.inbound.MessageEndpointWrapper.onMessage(MessageEndpointWrapper.java:131)
at com.ibm.mq.jms.MQSession$FacadeMessageListener.onMessage(MQSession.java:147)
at com.ibm.msg.client.jms.internal.JmsSessionImpl.run(JmsSessionImpl.java:2874)
at com.ibm.mq.jms.MQSession.run(MQSession.java:862)
at com.ibm.mq.connector.inbound.WorkImpl.run(WorkImpl.java:300)
at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:608)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1720)
Caused by: java.lang.RuntimeException: Problem during method invocation (onMessage)
... 12 more
Caused by: javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.pega.pegarules.pub.services.ServiceException: Caught exception while processing request for service VZWCSC.CM.InvokeDetailOrderNotifications, com.pega.pegarules.pub.PRException: Expecting a StreamMessage, received a message of type: com.ibm.jms.JMSMapMessage
From: (unknown)

Please suggest.


Show Less
To see attachments, please log in.
Low-Code App Development
Java and Activities
System Administration

Posted: 7 years ago
Posted: 7 Jun 2017 11:36 EDT
Sushant Samuel (SushantSamuel)
PEGA
Lead Service Assurance Advisor, Cloud Migrations
Pegasystems Inc.
IN

Hi pradeep,

Problem reported is same as described in below pdn article

https://community.pega.com/support/support-articles/problem-message-invocation-using-mdb-listener

Could you please verify your configuration as documented  in the below article

https://docs-previous.pega.com/deploying-jms-message-driven-bean-mdb-represents-jms-mdb-listener-pega-7

Thanks

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 7 Jun 2017 12:43 EDT
pradeep pydi (pradeepp2840)
Verizon Wireless
PEGA SENIOR SYSTEM ENGINEER
Verizon Wireless
US

Hi Sushant,

Thank you.Will check that.

On the other note,could you please help us understand a better way (PEGA OOTB activity) to find out the status of a listener via an alert/email .

PRPC version : PEGA 7.2.0

AES out of scope for us.

 

 

To see attachments, please log in.

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

Pega Collaboration Center 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