Support Article
Declare page corruption after some time
SA-961
Summary
After some time, a declare page gets corrupted. Each time it is used, an error is generated.
Error Messages
java.lang.NullPointerException
at com.pega.pegarules.engine.clipboard.XMLStream.writeXMLPage(XMLStream.java:561)
at com.pega.pegarules.engine.clipboard.XMLStream.clipboardToXML(XMLStream.java:437)
at com.pega.pegarules.engine.clipboard.WorkbenchXMLStream.<init>(WorkbenchXMLStream.java:179)
at com.pega.pegarules.engine.clipboard.ClipboardPageBase.getXML(ClipboardPageBase.java:1548)
at com.pega.pegarules.engine.clipboard.ClipboardPageBase.getXML(ClipboardPageBase.java:1520)
at com.pegarules.generated.activity.ra_action_getcurrencycodes_af8660e4006c7d40f3eb6657a041a103.step2_circum0(ra_action_getcurrencycodes_af8660e4006c7d40f3eb6657a041a103.java:183)
Steps to Reproduce
Use a declare page.
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules.
There is a race condition issue with declare page which trigger the errors.
Resolution
This issue is resolved by hotfix item Hfix-9581
Published June 12, 2015 - 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.