Support Article
Exception when restarting JBoss EAP 7.1 application server
SA-70877
Summary
Error generated in the log when restarting a JBoss EAP 7.1 application server.
Error Messages
SEVERE [com.pega.pegarules.internal.bootstrap.PRBootstrap] (localhost) Problem during method invocation (contextInitialized): java.lang.ExceptionInInitializerError
at com.pega.platform.message.internal.broadcast.NotificationModule.getInstance(NotificationModule.java:77)
at com.pega.platform.message.internal.broadcast.PRNotificationModule.<init>(PRNotificationModule.java:17)
at com.pega.platform.message.internal.broadcast.PRNotificationModule$NotificationModuleLoader.<clinit>(PRNotificationModule.java:27)
at com.pega.platform.message.internal.broadcast.PRNotificationModule.getInstance(PRNotificationModule.java:21)
at com.pega.pegarules.session.internal.serverpush.PushServerFactory.initialize(PushServerFactory.java:67)
at com.pega.pegarules.session.internal.serverpush.PushServerFactory.<init>(PushServerFactory.java:51)
at com.pega.pegarules.session.internal.serverpush.PushServerFactory.<clinit>(PushServerFactory.java:40)
at com.pega.pegarules.session.internal.serverpush.PushComponentProvider.getPushLifecycle(PushComponentProvider.java:48)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.initializePushEngine(WebAppLifeCycleListener.java:372)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:315)
at com.pega.pegarules.web.servlet.AbstractLifeCycleListener._contextInitialized_privact(AbstractLifeCycleListener.java:159)
at com.pega.pegarules.web.servlet.AbstractLifeCycleListener.contextInitialized(AbstractLifeCycleListener.java:73)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
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.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:92)
at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:205)
at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:174)
at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:239)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:99)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.lang.NullPointerException
at com.pega.pegarules.cluster.internal.PRClusterImpl.getPRSysStatusNodesInformation(PRClusterImpl.java:646)
at com.pega.pegarules.cluster.internal.PRClusterImpl.canInitialize(PRClusterImpl.java:313)
at com.pega.pegarules.cluster.internal.PRClusterImpl.getInstance(PRClusterImpl.java:237)
at com.pega.pegarules.cluster.internal.PRClusterProviderImpl.getInstance(PRClusterProviderImpl.java:97)
at com.pega.platform.message.CoreMessage.getInstance(CoreMessage.java:71)
at com.pega.platform.message.internal.broadcast.NotificationModule.<init>(NotificationModule.java:65)
at com.pega.platform.message.internal.broadcast.NotificationModule$NotificationModuleLoader.<clinit>(NotificationModule.java:58)
... 40 more
Steps to Reproduce
- Install JBoss EAP on Linux.
- Configure JBoss EAP to run as a Unix service.
- Restart JBoss EAP from the command line with the following instruction:
sudo service jboss-eap-rhel start
Root Cause
A defect or configuration issue in the operating environment.
The issue was caused because the JBoss was started in the past using the root account.
Therefore, this led to the extraction of root owned files in the Pega temporary directory and in the Pega log location. This prevented the Pega Engine to bootstrap correctly and to log bootstrap errors. Additionally, the Unix init.d service script pointed to the incorrect JBOSS_HOME environment variable causing a warning in the server logs.
Resolution
Make the following change to the operating environment:- Delete the Pega and JBoss temporary directories.
- Update JBOSS_HOME environment variable in /etc/default/jboss-eap.conf.
Published January 12, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.