Question

6
Replies
682
Views
Close popover
Pavan Ratnakar Vernekar (Pavan Vernekar)
Accenture

Accenture
AU
View Profile Send Message
Pavan Vernekar Member since 2014 1 post
Accenture
Posted: July 5, 2018
Last activity: July 9, 2018
Closed

JMS MDB listener configured failed to initialize

Hi All,

MDB listeners are not initialized post MDB ear updates and getting exception in WAS logs. Please advise

[7/3/18 21:32:15:213 AEST] 00000610 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 EngineBMT

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:95)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)

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

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.invokeMethod(AppServerBridgeToPega.java:273)

at com.pega.pegarules.internal.etier.mdb.PRJMSListenerBoot.onMessage(PRJMSListenerBoot.java:91)

at com.ibm.ejs.container.WASMessageEndpointHandler.invokeJMSMethod(WASMessageEndpointHandler.java:138)

at com.ibm.ws.ejbcontainer.mdb.MessageEndpointHandler.invokeMdbMethod(MessageEndpointHandler.java:1146)

at com.ibm.ws.ejbcontainer.mdb.MessageEndpointHandler.invoke(MessageEndpointHandler.java:844)

at com.sun.proxy.$Proxy25.onMessage(Unknown Source)

at com.ibm.mq.connector.inbound.MessageEndpointWrapper.onMessage(MessageEndpointWrapper.java:131)

at com.ibm.mq.jms.MQSession$FacadeMessageListener.onMessage(MQSession.java:133)

at com.ibm.msg.client.jms.internal.JmsSessionImpl.run(JmsSessionImpl.java:2911)

at com.ibm.mq.jms.MQSession.run(MQSession.java:958)

at com.ibm.mq.connector.inbound.ASFWorkImpl.doDelivery(ASFWorkImpl.java:97)

at com.ibm.mq.connector.inbound.AbstractWorkImpl.run(AbstractWorkImpl.java:235)

at com.ibm.ejs.j2c.work.WorkProxy$RunWork.run(WorkProxy.java:282)

at java.security.AccessController.doPrivileged(AccessController.java:426)

at javax.security.auth.Subject.doAs(Subject.java:494)

at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:133)

at com.ibm.ejs.j2c.work.WorkProxy$RunWork.run(WorkProxy.java:285)

at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)

at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:667)

at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)

[7/3/18 21:32:15:215 AEST] 00000610 AppServerBrid E com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega Problem during method invocation (onMessage)

javax.ejb.EJBException: Unable to locate implementation of PegaRULES Engine class for EngineBMT

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:95)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)

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

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.invokeMethod(AppServerBridgeToPega.java:273)

at com.pega.pegarules.internal.etier.mdb.PRJMSListenerBoot.onMessage(PRJMSListenerBoot.java:91)

at com.ibm.ejs.container.WASMessageEndpointHandler.invokeJMSMethod(WASMessageEndpointHandler.java:138)

at com.ibm.ws.ejbcontainer.mdb.MessageEndpointHandler.invokeMdbMethod(MessageEndpointHandler.java:1146)

at com.ibm.ws.ejbcontainer.mdb.MessageEndpointHandler.invoke(MessageEndpointHandler.java:844)

at com.sun.proxy.$Proxy25.onMessage(Unknown Source)

at com.ibm.mq.connector.inbound.MessageEndpointWrapper.onMessage(MessageEndpointWrapper.java:131)

at com.ibm.mq.jms.MQSession$FacadeMessageListener.onMessage(MQSession.java:133)

at com.ibm.msg.client.jms.internal.JmsSessionImpl.run(JmsSessionImpl.java:2911)

at com.ibm.mq.jms.MQSession.run(MQSession.java:958)

at com.ibm.mq.connector.inbound.ASFWorkImpl.doDelivery(ASFWorkImpl.java:97)

at com.ibm.mq.connector.inbound.AbstractWorkImpl.run(AbstractWorkImpl.java:235)

at com.ibm.ejs.j2c.work.WorkProxy$RunWork.run(WorkProxy.java:282)

at java.security.AccessController.doPrivileged(AccessController.java:426)

at javax.security.auth.Subject.doAs(Subject.java:494)

at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:133)

at com.ibm.ejs.j2c.work.WorkProxy$RunWork.run(WorkProxy.java:285)

at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)

at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:667)

at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)

[7/3/18 21:32:15:231 AEST] 000000c2 SystemOut O 2018-07-03 21:32:15,213 [AResourceAdapter : 0] [ ] [ ] [ ] ( etier.mdb.PRJMSListener) ERROR - PRPC Engine invocation failed, javax.ejb.EJBException: Unable to locate implementation of PegaRULES Engine class for EngineBMT

[7/3/18 21:32:15:234 AEST] 00000610 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /var/WebSphere/Logs/ffdc/PEGAMIRBGQC1auq4192lS01_f0524b6b_18.07.03_21.32.15.2265188168784012324052.txt com.ibm.ws.ejbcontainer.mdb.MessageEndpointHandler.invokeMessageListenerMethod 1010

[7/3/18 21:32:15:234 AEST] 00000610 LocalExceptio E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "onMessage" on bean "BeanId(PEGAMIRBGQC1_PRPC_j2ee14#prbeans.jar#CaseMgmtEventListenerL1, null)". Exception data: 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.WASMessageEndpointHandler.invokeJMSMethod(WASMessageEndpointHandler.java:138)

at com.ibm.ws.ejbcontainer.mdb.MessageEndpointHandler.invokeMdbMethod(MessageEndpointHandler.java:1146)

at com.ibm.ws.ejbcontainer.mdb.MessageEndpointHandler.invoke(MessageEndpointHandler.java:844)

at com.sun.proxy.$Proxy25.onMessage(Unknown Source)

at com.ibm.mq.connector.inbound.MessageEndpointWrapper.onMessage(MessageEndpointWrapper.java:131)

at com.ibm.mq.jms.MQSession$FacadeMessageListener.onMessage(MQSession.java:133)

at com.ibm.msg.client.jms.internal.JmsSessionImpl.run(JmsSessionImpl.java:2911)

at com.ibm.mq.jms.MQSession.run(MQSession.java:958)

at com.ibm.mq.connector.inbound.ASFWorkImpl.doDelivery(ASFWorkImpl.java:97)

at com.ibm.mq.connector.inbound.AbstractWorkImpl.run(AbstractWorkImpl.java:235)

at com.ibm.ejs.j2c.work.WorkProxy$RunWork.run(WorkProxy.java:282)

at java.security.AccessController.doPrivileged(AccessController.java:426)

at javax.security.auth.Subject.doAs(Subject.java:494)

at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:133)

at com.ibm.ejs.j2c.work.WorkProxy$RunWork.run(WorkProxy.java:285)

at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)

at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:667)

at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)

Caused by: javax.ejb.EJBException: Unable to locate implementation of PegaRULES Engine class for EngineBMT

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:95)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)

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

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.invokeMethod(AppServerBridgeToPega.java:273)

... 19 more

Close popover
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 2 years ago
Close popover
Devarajulu Prathapaneni (Deva_Prathapaneni)
Cognizant
Tech Lead
Cognizant
SE
View Profile Send Message

Hi,


Did you performed all the required configuration in WAS.


1. Creating JNDI and mapping MQ details.


2. Configuring of Queuemanager.


3. Configuring of activation specific and listener port.


Please share the configuration files(bindign xml and ejb.jar xml´s)


Thanks,


Deva

Posted: 2 years ago
Close popover
Pavan Ratnakar Vernekar (Pavan Vernekar)
Accenture

Accenture
AU
View Profile Send Message

Hi Deva,


Thanks for Response. 


All WAS related configuration are completed. Attached the binding and ejb-jar.xml files for reference.


We tried to add below tags (bold) in to ejb-jar.xml


<message-driven-destination id="MessageDrivenDestination_CaseMgmtEventListenerL2">


                     <message-destination-type>javax.jms.Queue</message-destination-type>


</message-driven-destination>


 


But, the ear deployment via u-deploy itself failed with below error


ADMA5057E: Application validation failed with an unexpected exception while checking module to server relationship: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: META-INF/ejb-jar.xml

ADMA5011I: The cleanup of the temp directory for application PEGAXXXXXC1_PRPC_j2ee14 is complete.
ADMA5014E: The installation of application PEGAXXXXXC1_PRPC_j2ee14 failed.
ADMA5057E: Application validation failed with an unexpected exception while checking module to server relationship: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: META-INF/ejb-jar.xml


ADMA5011I: The cleanup of the temp directory for application PEGAXXXXXC1_PRPC_j2ee14 is complete.
ADMA5014E: The installation of application PEGAXXXXXC1_PRPC_j2ee14 failed.


Please advice.

Posted: 2 years ago
Close popover
Marc Lasserre (MarcLasserre_GCS)
PEGA
Principal Software Solutions Engineer
Pegasystems Inc.
FR
View Profile Send Message

Hello,


The error is likely due to the fact that there were messages in the queue during server startup. Depending on the timing of the message processing, the Pega engine may not be ready, and hence the error you having.

Posted: 2 years ago
Close popover
Simon Chan (chans3)
PEGA
Principal GCS Solutions Engineer
Pegasystems Inc.
GB
View Profile Send Message

Hi Pavan,


I have experienced similar issue with JMSMDB on Websphere 8.5 before. It occurred when the server runs on Java 8. Luckily, it can be addressed by deploying WebSphere patch of IBM IFPI73197. After the patch has been deployed, the modified prpc_j2ee14_ws.ear containing the updated deployment descriptors must also be redeployed.


Regards

Simon

Posted: 2 years ago
Close popover
Domenico Giffone (DomenicoGiffone_GCS)
PEGA
Principal Software Solutions Engineer
Pegasystems Inc.
IT
View Profile Send Message

Simon recommended the best solution. Alternate approaches are:

https://community.pega.com/knowledgebase/articles/websphere-log-error-java-8-enterprise-javabeans


https://community.pega.com/support/support-articles/classnotfoundexception-installing-pega-722-was-85511


 
Share this page Share via LinkedIn Copying...
Copied!