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
We are looking for recommendations on tuning the CMS parameters and suggestions on what CMSInitiatingOccupancyFraction value to use?
- Oracle Java
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.