Support Article

After passivation clipboard page remove is not working

SA-38316

Summary



After passivation clipboard page remove is not working.


Error Messages



Not Applicable


Steps to Reproduce


Not Applicable


Root Cause



A defect in Pegasystems’ code for which once reference property is passivated its reference is lost.

Due to this, Null pointer is thrown because existence of the reference is not checked before trying to do operations on it.

Resolution



Detail about parent Hfix and dependents:-


Hotfix Subject Instructions
Hfix-29785 (Parent) After passivation clipboard page remove is not working Re-start nodes after applying hotfix
HFix-21456 Value list no longer indexing Restart
Hfix-21456 Issue creating new page with page new method NA
Hfix-22753 Exception on Read Only Property - Data Page NA
Hfix-23343 passivation issue with reports in case manager portal NA
Hfix-27671 Diag: English sporadically displayed with spanish locale set Add the below mentioned lines in prlogging.xml which is located in prweb war file (Example : E:\apache-tomcat-7.0.55\webapps\prweb\WEB-INF\classes\prlogging.xml)

<appender name="SRlogger" class="com.pega.pegarules.priv.util.FileAppenderPega">
<param name="FileNamePattern" value="'@{web.tmpdir}/SRA24414logger-'yyyy-MMM-dd'.log'"/>
<param name="MaxFileSize" value="500MB" />
<layout class="com.pega.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d [%20.20t] [%10.10X{pegathread}] [%20.20X{tenantid}] [%20.20X{app}] (%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n"/>
</layout>
</appender>

<category name="SR-B51262" additivity="false">
<priority value="info" />
<appender-ref ref="SRlogger" />
</category>


Later after restring the server, navigate through DesignerStudio->System->Operations->Logs, open logLevelSettings ,select " SR-B51262" and set log level to 'Debug'.

After the issue is reproduced please reset back to INFO level.
Hfix-20015 717 startup on Windows OS with non-english locale fails NA
Hfix-20115 Upgrade to ML7: Data Pages not getting loaded onto clipboard If the user is unable to login to designer studio to import the hotfix, then follow the instructions mentioned in the below article which describes how to import an archive(hotfix) using command line

https://pdn.pega.com/system-operations/how-to-import-or-export-an-archive-from-the-command-line
Hfix-21825 Data Page parallel loading cannot access requester level pages NA
Hfix-24807 Memory leak while using defered load Code based hotfix, would require server re-start.
Hifx-26204 ADP Background Requestor lacks production and localized ruleset Restart the nodes after installing the hotfix
Hfix-23912 Unexpected localization after passivation occurs NA
Hfix-27330 Asynchronous data page load failure Restart the node after installing the hotfix
Hfix-28426 Batch requestor localization ruleset usage incorrect After installing this HFix please restart the server
Hfix-21137 System pulse is not synching nodes After installing hotfix from intranet node . Restart the intranet nodes and webnodes once to pick up the latest code changes.

Now Please enable debug logging level on VTableTrace from SMA on web node only. Now try out the test scenario and disable the logger level.

Alternatively you can enable debug log from prlogging.xml with the following entry.

<category name="VTableTrace">
<priority value="debug" />
</category>
Hfix-20475 Events not firing since upgrading to Pega 7.1.7 Since it's an engine HFIX a restart would be required.
Hfix-20560 Tomcat startup fails due to custom Tomcat version string If you are using a (custom) Tomcat instance (Merge will be disabled by default) but the custom tomcat is a current version (7+), then enable merge using PRPC config for each datasource (pegadata and pegarules in this example):

<env name="database/databases/pegadata/useMerge" value="true" />
<env name="database/databases/pegarules/useMerge" value="true" />

If you are using a (custom) Tomcat instance (Merge is disabled by default) but the tomcat is a not a current version (< 7), then Merge cannot be enabled, and the you should be encouraged to use a newer, supported version of Tomcat.
Hfix-20635 Diagnostic Hotfix: Not getting results more than 50 from RD This is Diagnostic hotfix should not commit the hotfix. After collecting the debug information This should be rolled back.

Logger levels should be reset to previous values.
Hfix-20804 Diagnostic Patch: RDfails to fetch more than 50 records from DB NA


Please follow the below generic instructions to install the Hotfix (Recommended).

  1. Please take full backup of your Database.
  2. To install the Hotfix, navigate Designer Studio->system->Release->Hotfix Manager->Install Hotfix
  3. Stop application server and remove the contents (folders and files) of Pega temp directory in application server.
  4. Or do a clean re-start of the application server by removing the PegaRULES_Extract_Marker file.
  5. Clear browser cache and login to application and test the scenario.

Published May 20, 2017 - Updated June 9, 2017

Have a question? Get answers now.

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