Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega server cannot start after server restart



At first there is an error when user tried to create a new case type (there is an error with @Baseclass) So user restarted the server.

After server start up, JBoss successfully up and deployed prhelp and prsysmgmt (it can accessed); but while deploying prweb it crash with an info like "[LOCAL] [564462a54e8efab83241814626c1214c] [3.4.1] Interfaces is disabled, trying to pick one address from TCP-IP config addresses: []" and all deployed apps got undeployed.

Error Messages

2017-02-03 14:49:49,383 [ pegalinux] [ STANDARD] [ ] [ ] ( priv.context.JNDIEnvironment) ERROR - Exception during getEJBInstance "com.pega.pegarules.internal.etier.interfaces.EngineLocalHome"
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(

Steps to Reproduce

This occurs when Pega starts up a single node system.

Root Cause

Deployment of prpc_j2ee14_jboss61JBM.ear was taking longer time than the timeout configured on JBoss.


Below change resolved the behavior.

Change configuration:

<property name="" value="600"/> to
<property name="" value="10800"/>

Suggest Edit

Published February 20, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us