Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Issue: Performance Analyzer Tool locks up

Updated on September 25, 2019

Symptom

The Performance Analyzer (PAL) is a collection of counters and timer readings that a developer can use to analyze performance in a system. You can access PAL from the Developer Portal by selecting Run > Performance.

When you access this tool, the Performance Summary window appears below your main window and the following message displays:

Gathering performance data .. please wait

In some instances, this message remains on your screen and the performance data does not appear. In this case, the following error appears in the log file:

com.pega.pegarules.pub.PRRuntimeException
Illegal characters detected in the path"/StaticContent/personal/73e3b096647a213a419e210d19ca52ea/8ss5droqenscigegcb_2dgvg%5b*%2f!developer". You may not use ", ?, *, <, >, |,
PegaRULES 5.2 General Availability (v52_relcand_0044)
com.pega.pegarules.pub.PRRuntimeException: Illegal characters detected
in the path"/StaticContent/personal/73e3b096647a213a419e210d19ca52ea/8ss5droqenscigegcb_2dgvg%5b*%2f!developer". You may not use ", ?, *, <, >, |, :
at com.pega.pegarules.priv.storage.StorageUtils.getFile(StorageUtils.java(C
ompiled Code))
at com.pega.pegarules.pub.util.PRFile.(PRFile.java(Compiled Code))
at com.pega.pegarules.web.staticcontent.StaticContentClient.serveFile(Stati
cContentClient.java:703)
at com.pega.pegarules.web.staticcontent.StaticContentClient.retrieveFile(St
aticContentClient.java:556)
at com.pega.pegarules.web.impl.WebStandardImpl.runStaticContentRequest(WebS
tandardImpl.java:812)
at com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:
156)
at com.pega.pegarules.web.servlet.WebStandard.doPost(WebStandard.java:87)
at com.pega.pegarules.web.servlet.WebStandard.doGet(WebStandard.java:76)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.ja
va:1282)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrap
per.java:673)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheS
ervletWrapper.java:80)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1802)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:8 4)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscriminatio
n(HttpInboundLink.java:469)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformatio
n(HttpInboundLink.java:408)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLi
nk.java:286)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscr
iminaters(NewConnectionInitialReadCallback.java:201)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(Ne
wConnectionInitialReadCallback.java:103)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueMa
nager.java:566)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.
java(Compiled Code))
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.
java:952)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager
.java:1039)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
Caused by: java.lang.IllegalArgumentException: Illegal characters
detected in the path
"/StaticContent/personal/73e3b096647a213a419e210d19ca52ea/8ss5droqenscig
egcb_2dgvg%5b*%2f!developer". You may not use ", ?, *, <, >, |, :
at com.pega.pegarules.priv.storage.StorageUtils.normalizeRelativePath(Stora
geUtils.java(Compiled Code))
at com.pega.pegarules.storage.FileStorageManager.getFile(FileStorageManager
.java(Compiled Code))
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
... 25 more

 

Solution

Workaround

To work around this issue, adjust your preferences to open the Performance tool in a separate window, as follows:

  1. Select Edit > Preferences to display the Desktop Preferences dialog:

  2. Select Tools from the left-hand tree control; the Tools Preferences appear on the right:

  3. Select the Performance check box.
  4. Click Save; the dialog closes saving your changes.
  • Previous topic Issue: Java 64K Method Size Limit
  • Next topic Issue: Process Commander applications monitored with CA Wily Introscope might experience depleted native memory

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us