Support Article

Not able to start service with Pega war file

SA-33210

Summary



Server is not able to start with the deployed war file of Pega.

Error Messages



Errors seen in logs:

Could not connect to: /xxx.xxx.xxx.xxx:5701. Reason: SocketException[Connection refused to address /xxx.xxx.xxx.xxx:5701]

​ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS013412: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '

ERROR - [setRunState] Exception occured while setting RunState
com.pega.pegarules.pub.PRRuntimeException: caught database exception during property definition lookup for RULE-OBJ-PROPERTY SYSTEM-STATUS-NODES PYRUNSTATE #20130918T234905.112 GMT
at com.pega.pegarules.data.internal.dictionary.DictionaryCacheImpl.getPropertyDefinitionByKey(DictionaryCacheImpl.java:246)

ERROR - [updateActiveUserCount] Exception occured while updating active user count
com.pega.pegarules.pub.PRRuntimeException: caught database exception during property definition lookup for RULE-OBJ-PROPERTY SYSTEM-STATUS-NODES PYACTIVEUSERCOUNT #20130919T003926.949 GMT


Steps to Reproduce



Not Applicable

Root Cause



A defect or configuration issue in the operating environment, find the analysis below for each error respectively:

Could not connect to: /xxx.xxx.xxx.xxx:5701. Reason: SocketException[Connection refused to address /xxx.xxx.xxx.xxx:5701]:
  • The deployment timeout on application server (JBOSS 6.4 EAP) was set to 300 seconds (5 minutes), since the deployment was not finished in 5 minutes, observe this timeout error and the node leaves the cluster everytime this error occurs since JBoss was rolling back the startup request.


ERROR - [setRunState] Exception occured while setting RunState
com.pega.pegarules.pub.PRRuntimeException: caught database exception during property definition lookup for RULE-OBJ-PROPERTY SYSTEM-STATUS-NODES PYRUNSTATE #20130918T234905.112 GMT
at com.pega.pegarules.data.internal.dictionary.DictionaryCacheImpl.getPropertyDefinitionByKey(DictionaryCacheImpl.java:246)

  • The Startup agents were failing due to which the pyRunState property couldn't be set in pr_sys_statusnodes table


[updateActiveUserCount] Exception occured while updating active user count
com.pega.pegarules.pub.PRRuntimeException: caught database exception during property definition lookup for RULE-OBJ-PROPERTY SYSTEM-STATUS-NODES PYACTIVEUSERCOUNT #20130919T003926.949 GMT

  • The Startup agents were failing due to which the pyActiveUserCount property couldn't be set in pr_sys_statusnodes table


Resolution




Make the following change to the operating environment:

Increase the deployment timeout with settings as below to be set before starting the server.

The following settings will extend the deployment and System Management Application (SMA) operation timeout to 10 minutes:

  1. Djboss.as.management.blocking.timeout=600​
  2. Dorg.jboss.remoting-jmx.timeout=600

Published February 2, 2017 - Updated February 20, 2017

Have a question? Get answers now.

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