exception during invocation of method "onMessage" The MDB Listener Service activity is not being called.
When we put the message in the queues, We are observing the below error and service activity is not being called. Whenever there is a message in queue, it encounters below mentioned error and listeners stop running in WAS.
Please advise.
Steps followed
When we put the message in the queues, We are observing the below error and service activity is not being called. Whenever there is a message in queue, it encounters below mentioned error and listeners stop running in WAS.
Please advise.
Steps followed
- Created the connection factory and queues in WAS
- Used JNDI names in configuring the JMS MDB Listener (Destination Queue JNDI name)
- Updated the ejb-Jar.xml in the prbeans.jar (using 7zip)
- Updated the application and used add/replace module of WAS and deployed the updated prbeans.jar
- Used Listener ports for binding the listeners and enterprise beans
- Imported the Jar files in Pega - com.ibm.mq.connector.jar, com.ibm.mq.jar, com.ibm.mq.jmqi.jar
- Restarted the servers
[15/06/17 13:26:24:858 CST] 0000017a MDBListenerIm I WMSG0042I: MDB Listener MBLCCMSMaterDataListener started successfully for JMSDestination jms/MBLCMasterData
[15/06/17 13:26:24:889 CST] 00000088 SystemOut O 2017-06-15 13:26:24,889 [stenerThreadPool : 0] [ STANDARD] [ ] [ ] ( etier.mdb.PRJMSListener) ERROR - PRPC Engine invocation failed, javax.ejb.EJBException: Unable to locate implementation of PegaRULES Engine class for EngineCMT
[15/06/17 13:26:24:889 CST] 00001371 PRBootstrap E com.pega.pegarules.internal.bootstrap.PRBootstrap Problem during method invocation (onMessage)
javax.ejb.EJBException: Unable to locate implementation of PegaRULES Engine class for EngineCMT
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.callEngine(PRJMSListener.java:200)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.init(PRJMSListener.java:175)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.onMessage(PRJMSListener.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:94)
[15/06/17 13:26:24:889 CST] 00001371 LocalExceptio E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "onMessage" on bean "BeanId(prpc_j2ee14_ws#prbeans.jar#MBLCCMSMasterDataListener, null)". Exception data: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:94)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:619)
at com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessionDispatcher.java:47)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:100)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:132)
at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:581)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1864)
Caused by: java.lang.RuntimeException: Problem during method invocation (onMessage)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:278)
at com.pega.pegarules.internal.etier.mdb.PRJMSListenerBoot.onMessage(PRJMSListenerBoot.java:91)
at com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnMessage.run(MDBWrapper.java:309)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
at com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage(MDBWrapper.java:266)
at com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:235)
at com.ibm.mq.jms.MQSession$FacadeMessageListener.onMessage(MQSession.java:133)
at com.ibm.msg.client.jms.internal.JmsSessionImpl.run(JmsSessionImpl.java:2799)
at com.ibm.msg.client.jms.internal.JmsXAQueueSessionImpl$1.run(JmsXAQueueSessionImpl.java:1007)
at com.ibm.mq.jms.MQSession.run(MQSession.java:958)
at com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:1056)
at com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage(ServerSession.java:1090)
at com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:760)
at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:726)
... 9 more
Caused by: javax.ejb.EJBException: Unable to locate implementation of PegaRULES Engine class for EngineCMT
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.callEngine(PRJMSListener.java:200)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.init(PRJMSListener.java:175)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.onMessage(PRJMSListener.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:94)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:619)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:367)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:408)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272)
... 22 more
[15/06/17 13:26:24:905 CST] 00001371 ServerSession E com.ibm.ejs.jms.listener.ServerSession run WMSG0036E: Maximum message delivery retry count of 0 reached for MDB MBLCCMSMasterDataListener, JMSDestination jms/MBLCMasterData, MDBListener stopped
[15/06/17 13:26:24:936 CST] 000218d9 MDBListenerIm I WMSG0043I: MDB Listener MBLCCMSMaterDataListener stopped for JMSDestination jms/MBLCMasterData
Pegasystems Inc.
IN
Hi From the below exception message
javax.ejb.EJBException: Unable to locate implementation of PegaRULES Engine class for EngineCMT
have you added deployment descriptor to ejb-jar.xml file? if added can you verify the EngineCMT mode is true or not in this case your running listener in CMT mode it should be true.
please make the above change and restart the server.
Thanks
Narasimha
Pegasystems Inc.
US
Hello,
The JMS MDB Listener is throwing Exceptions because the IBM WAS begins message consumption from the JMS destination as soon as the activation specification is used for a message-driven bean which is before the PegaRULES engine (EJBs) have fully initialized.
WebSphere Application Server supports the use of custom properties to define WebSphere MQ properties.
You can use this task to set custom properties for JMS destinations, connection factories, and activation specifications for the WebSphere MQ messaging provider. For example, you would use this task to set the custom property WAS_EndpointInitialState for an activation specification. WAS_EndpointInitialState determines whether or not message consumption begins from the JMS destination as soon as the activation specification is used for a message-driven bean to connect with the destination.
Refer to IBM Support Article below for complete implementation details -
~Ankur