404-error on css
The Designer Studio is sporadically not rendering correctly; and we see corresponding HTTP 404 errors regarding CSS files in the logs.
Here is an example screenshot of what is seen instead of the usual Designer Studio screen: (Screenshot if from Firefox).
Note: It was found that Firefox and Chrome browsers show similar results to the screenshot above when the issue is present: it was found that Internet Explorer may render the issue differently.
2015-02-11 13:01:25,251 [ WebContainer : 2] [ STANDARD] [ ] (ticcontent.StaticContentClient) ERROR - 404 on request: /OALFpahD0ZRP3etG7NtAKR29eVUPuyxLpBoc-Tm1SyY[*/webwb/pzskinv2_pzdesignerstudio_e274d6b1d99b8
873b2a0f79102cd267ad0540edfa641ed958d7099ff60b63bf3_0--4_1706179809.css!!.css; Referring URL: http://xxxx/prweb/PRServlet/OALFpahD0ZRP3etG7NtAKR29eVUPuyxLpBoc-Tm1SyY%5B*/!STANDARD?pzPostData=812216027; Requestor ID: HB429B1AFFCAD0984AF5E65ADC15BD64A
Steps to Reproduce
The issue will appear to happen randomly : this is due to the fact that an Agent running in the background is responsible for clearing out unused Static Content - the Activity that the Agent runs was found to be deleting CSS files needed by Designer Studio (they were being identified as 'unused' incorrectly by the Agent).
The root cause of this problem is a defect in Pegasystems’ code/rules.
The Activity "PZDELETEORPHANSTATICCONTENT" (called from the Out-of-The-Box Agent "DeleteUnusedStaticContentFiles") was found to be deleting CSS files that should not have been deleted.
(Note: The Agent was NOT found to *always* delete the CSS files in every run : the internal logic of the Activity and the state of the system (including client-side browser caches) mean the issue is not easily predictable.)
HFIX-22715 should be installed in order to correct the Activity "PZDELETEORPHANSTATICCONTENT" such that it does not delete CSS files needed by the Designer Studio.
40% found this useful