Application not Starting up - java.lang.NoClassDefFoundError: com/hazelcast/core/LifecycleListener
Hi
Our Application is not starting because of below error. Log attached. Which table has the class details stored? "com/hazelcast/core/LifecycleListener"
SEVERE: Problem during method invocation (contextInitialized)
java.lang.ExceptionInInitializerError
Caused by: java.lang.RuntimeException: Unable to create PRModulesProvider
java.lang.NoClassDefFoundError: com/hazelcast/core/LifecycleListener
Caused by: java.lang.NoClassDefFoundError: com/hazelcast/core/LifecycleListener
***Edited by Moderator: Lochan to update platform capability tags***
Pegasystems Inc.
IN
Hi Arvind,
Your application is deployed in how many nodes?Can you verify pr_engine classes table.
com/hazelcast/core/LifecycleListener will be part of hazelcast jar.Please compare engine_classes table with of working scenario.
Thanks,
Abhinav
Pegasystems Inc.
IN
Hi Arvind,
Can you share me data of pr_engine_class table.I suspect hazelcast jar is missing in that table.
Thanks,
Abhinav
BNYMellon Technology
IN
Thanks Abhinav, the table has 300k records, tough to send. And We got solution from Pega team when we raised an SR. Will post that as final response. Thanks again.
Ford Motor Company
US
Arvind, I suspect issue with your unix account, either it may not have enough privileges or possible ports blocked, you might need to engage your unix administrator to see no blocks or privilage issue during the JVM start up.
Similar error stack:
BNYMellon Technology
IN
Hi
The issue happened because of a hotfix (SR-D19000 ) we received for an issue (Reindexing Work not working). When we did the rollback, the tables got corrupted. We received solution from pega team.
"
The cause of the issue is that the hotfix I shared earlier included a custom action to move the previous shipped hazelcast version to a separate codeset version on the next system startup. This ensures that the new version of hazelcast is loaded, and not the old one. Hotfix rollback was not aware of this custom action and so was not able to restore the original version of the hazelcast jar. To correct this, the you would need to execute custom SQL to restore the original version. Alternatively we have created this hotfix that applies the SQL automatically.
After installing this hotfix, the application server needs to be restarted. After restarting, the original hotfix can then be rolled back. As a side effect, this hotfix will end up being rolled back as well. This is okay, as it only needs to exist during the rollback process. This hotfix should never be ported to another release.
I've already tested this in my local Pega 7.4 setup, and it worked for me.
"