Skip to main content


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

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.

JVM properties for IBM WebSphere Application Server

Updated on September 13, 2021

The Java Virtual Machine (JVM) properties for IBM WebSphere Application Server require minimal configuration changes to operate at optimum levels for Pega 7 applications. However, you can configure the JVM to analyze the performance of garbage collection by setting the following logging parameters:

  • For IBM WebSphere Application Server, Version 8 and later, set the garbage collection policy by specifying the property -Xgcpolicy:balanced.
  • For versions of IBM WebSphere Application Server that are earlier than Version 8:
    • Set the garbage collection policy to Generational concurrent (gencon) by specifying the property -Xgcpolicy:gencon.
    • Disable explicit garbage collection by specifying the -Xdisableexplicitgc property.
  • On the Configuration tab of the Process definitions window for the JVM server, set the following values:
    • Specify 4096 MB for both the Initial heap size and Maximum heap size fields.
    • Select the Verbose garbage collection check box.

You can navigate to the Process definitions window for the JVM server from the Applications server window. Under the Server Infrastructure section, expand the Java and Process Management menu and select Process definitions.

  • Previous topic JVM options for Oracle Java HotSpot Virtual Machine
  • Next topic Memory management revealed - Questions and answers

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