Support Article
Error 503: PegaRULES server not available
Summary
After recycling the Application server, error is observed when trying to login.
Error 503: PegaRULES server not available.
Error Messages
[12/14/15 9:37:59:682 CST] 00000023 SystemOut O 2015-12-14 09:37:59,678 [] ( etier.engine.EngineStartup) ERROR - PegaRULES initialization failed. Server: testserver
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
Caused by:
java.lang.IllegalStateException
at com.ibm.ejs.container.BMStatelessBeanO.setRollbackOnly(BMStatelessBeanO.java:68)
at com.pega.pegarules.pub.context.PRSessionContext.setRollbackOnly(PRSessionContext.java:165)
at com.pega.pegarules.engine.database.ThreadConnectionStore.endTransaction(ThreadConnectionStore.java:195)
at com.pega.pegarules.engine.database.ThreadConnectionStore.rollback(ThreadConnectionStore.java:328)
at com.pega.pegarules.engine.database.DatabaseImpl.attemptToProcessUpdates(DatabaseImpl.java:1630)
at com.pega.pegarules.engine.database.DatabaseImpl.processUpdates(DatabaseImpl.java:1462)
at com.pega.pegarules.engine.database.Saver.save(Saver.java:520)
at com.pega.pegarules.engine.database.DatabaseImpl.save(DatabaseImpl.java:3674)
at com.pega.pegarules.engine.database.DatabaseImpl.save(DatabaseImpl.java:3658)
at com.pega.pegarules.engine.context.PRNodeImpl.updateLastIndexBuildDateTime(PRNodeImpl.java:1469)
at com.pega.pegarules.engine.context.PRNodeImpl.doIndexInit(PRNodeImpl.java:1411)
at com.pega.pegarules.engine.context.PRNodeImpl.startNode(PRNodeImpl.java:1328)
at com.pega.pegarules.engine.context.PREnvironment.finishInit(PREnvironment.java:1229)
Steps to Reproduce
There is no specific use case to replicate this behavior.
Root Cause
A defect in Pegasystems’ code or rules.
Resolution
Apply HFix-25660
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.