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 startup fails StringIndexOutOfBoundsException due to logs



 Pega application will not process after user restarts the appserver. Relevant PDN article - "PegaRULES-FirstLogCreationTime.log and PegaRULES-ALERT-FirstLogCreationTime.log file are of zero byte size in the file system. PRPC finds this file in the file system and throws the above exception."

Error Messages

log4j:ERROR Cannot write to /usr/WebSphere/AppServer/profiles/AppSrv/temp/WASNode_cs1bcmapd01/appserver01/

[10/30/16 19:47:14:288 EDT] 0000007c PRBootstrap   E com.pega.pegarules.internal.bootstrap.PRBootstrap  Problem during method invocation (contextInitialized) java.lang.StringIndexOutOfBoundsException
    at java.lang.String.<init>(
    at com.pega.pegarules.priv.util.LogDeleteUtil.readFromFile(

Steps to Reproduce

Restart appserver. (Pega does not come up)

Root Cause

The root cause for this scenario is that a file system storage space issue results in the presence of zero byte file in log directory (PegaRULES-FirstLogCreationTime.log).


Refer to PDN article to get instance up and running -

Install HFix-30333 to prevent this issue in the future.

Suggest Edit

Published November 10, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

100% found this useful

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