Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Performance issues related to memory with Pega 7.1.8

SA-17306

Summary



User has reported generation of a huge number of heap dumps in log files and downgraded system performance.
Unless user deletes those files from server, it is not possible to even restart the server.

Error Messages



2015-11-04 03:51:46,771 [   WebContainer : 13] (FilesystemCompilationSaver) ERROR a.server1|b.server1 - Problem saving Java source file to filesystem
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:291)
at com.pega.pegarules.pub.util.PROutputStream.write(PROutputStream.java:181)
at com.pega.pegarules.exec.internal.util.UTF8OutputStreamWriterImpl.flushCharBufferToStream(UTF8OutputStreamWriterImpl.java:213)
at com.pega.pegarules.exec.internal.util.UTF8OutputStreamWriterImpl.write(UTF8OutputStreamWriterImpl.java:154)
at com.pega.pegarules.exec.internal.util.UTF8OutputStreamWriterImpl.write(UTF8OutputStreamWriterImpl.java:139)
at com.pega.pegarules.exec.internal.util.OSFileUtilsImpl.writePRFile(OSFileUtilsImpl.java:670)
at com.pega.pegarules.exec.internal.util.OSFileUtilsImpl.writePRJavaSource(OSFileUtilsImpl.java:961)
at com.pega.pegarules.generation.internal.compiler.FilesystemCompilationSaver.saveSources(FilesystemCompilationSaver.java:119)
at com.pega.pegarules.generation.internal.compiler.PRCompilerUtil.notifyCompilationListeners(PRCompilerUtil.java:785)
at com.pega.pegarules.generation.internal.compiler.PRCompilerEclipse._compile_privact(PRCompilerEclipse.java:575)
at com.pega.pegarules.generation.internal.compiler.PRCompilerEclipse.compile(PRCompilerEclipse.java:502)
at com.pega.pegarules.generation.internal.compiler.PRCompilerEclipse.compile(PRCompilerEclipse.java:469)
at com.pega.pegarules.generation.internal.compiler.PRCompilerEclipse.compile(PRCompilerEclipse.java:403)
at com.pega.pegarules.generation.internal.compiler.PRCompilerEclipse.compile(PRCompilerEclipse.java:327)
at com.pega.pegarules.generation.internal.assembly.FUAManagerImpl.edit(FUAManagerImpl.java:759)
at com.pega.pegarules.generation.internal.PRGenProviderImpl.edit(PRGenProviderImpl.java:520)
at com.pega.pegarules.session.internal.mgmt.Executable.checkJavaGeneration(Executable.java:3097)
at com.pegarules.generated.activity.ra_action_validate_10955f9b88be9fcf1d93cd46fb69ae37.step10_circum0(ra_action_validate_10955f9b88be9fcf1d93cd46fb69ae37.java:1007)
at com.pegarules.generated.activity.ra_action_validate_10955f9b88be9fcf1d93cd46fb69ae37.perform(ra_action_validate_10955f9b88be9fcf1d93cd46fb69ae37.java:240)
..more..



Steps to Reproduce



Enable heap dump generation at IBM Websphere application server end.

Root Cause



User has the heap dump generation enabled at their IBM Websphere application server instance that is consuming the file space rapidly.

Exception message states that there is no space left on drive and thus the error while saving Java source file to filesystem.


Resolution



Solution is to increase the file space as required, there is no recommendation as far as application is concerned.

If the heap dumps generated are not required, then it can be turned off.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us