What is an optimal value for the Concurrent Mark Sweep Collector (CMS) parameter -XX:CMSInitiatingOccupancyFraction?

Solution Unverified - Updated -

Issue

One of our SOA-P servers has started throwing long response times, and after we confirmed that Garbage Collector (GC) Concurrent Mark Sweep (CMS) was killing it, we pulled it from the Load Balancer.

The garbage collector logs are full of concurrent mode failure entries. It seems like CMS is starting too late to keep up. We confirmed that the JBOSS settings are the default for -XX:CMSInitiatingOccupancyFraction.

We are looking for recommendations on tuning the CMS parameters and suggestions on what CMSInitiatingOccupancyFraction value to use?

Environment

  • Oracle Java

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content