Problem Starting Listener after upgrading to 7.4
Hi
I upgraded Pega from 7.1.5 to 7.4. We are unable to start the listener. Getting below error. Pls assist
| Start Listener Status |
| Listener 'Data-Admin-Connect-MQListener:ICS.ClientQTTEICS(com.pega.pegarules.integration.engine.internal.services.mq.MQListener)' failed to start because of the following error: |
| Caught exception while launching service listener ICS.ClientQTTEICS of type Data-Admin-Connect-MQListener, java.lang.NoClassDefFoundError: Could not initialize class com.pega.pegarules.integration.engine.internal.services.mq.MQListener |
***Edited by Moderator: Lochan to update platform capability tags***
PEG
GB
Is this producing any kind of stack in the logs which may indicate the underlying cause.
I assume you've already queried pr_engineclasses directly to very you have this class. Something like
select * from pega74rules.pr_engineclasses
where pzclass like 'MQListener%'
Also when is this listener starting. Is this during system boot? If so, is the error before the engine initializes?
BNYMellon Technology
IN
Hi,
Thanks for the response. We are starting the listener from SMA. Below is the error from the log
Hi,
Thanks for the response. We are starting the listener from SMA. Below is the error from the log
java.lang.NoClassDefFoundError: Could not initialize class com.pega.pegarules.integration.engine.internal.services.mq.MQListener at java.lang.Class.forName0(Native Method) ~[?:1.8.0_212] at java.lang.Class.forName(Class.java:264) ~[?:1.8.0_212] at com.pega.pegarules.integration.engine.internal.services.listener.ServiceListenerBaseImpl.getInstance(ServiceListenerBaseImpl.java:330) ~[printegrint.jar:?] at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.launchListener(ListenerWrapper.java:149) ~[printegrint.jar:?] at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startOneListener(ListenerStateManagerImpl.java:762) ~[printegrint.jar:?] at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startListener(ListenerStateManagerImpl.java:667) ~[printegrint.jar:?] at com.pega.pegarules.management.internal.system.operations.StartListenerOnLocalNodeCommand.startListener(StartListenerOnLocalNodeCommand.java:81) ~[prprivate.jar:?] at com.pega.pegarules.management.internal.ListenerManagementAPI.Start(ListenerManagementAPI.java:283) ~[prprivate.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_212] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_212] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_212] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_212] at com.pega.pegarules.management.internal.MB2EngineAccess.invoke(MB2EngineAccess.java:169) ~[prprivate.jar:?] at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invoke_privact(EngineImpl.java:408) ~[prprivate.jar:?] at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.run(EngineImpl.java:393) ~[prprivate.jar:?] at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImp...truncated
actually we did the upgrade in Dev, running scripts. In QA we just moved the Rule schema from Dev. Will that be the issue?