Garbage Collection on Java Process Shows Error "concurrent mode failure"
Last updated on NOVEMBER 05, 2016
Applies to:Oracle Containers for J2EE - Version 10.1.3.1.0 to 10.1.3.5.0 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 22-Apr-2013***
***Checked for relevance on 08-DEC-2014***
Find that an application gets very slow when garbage collection cannot finish in time. It starts retrying and this causes the instance to slow down. Java garbage collection parameters have already been tweaked, and for garbage collection reporting, also "-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps" are set. The logfile / output file of OC4J shows following entry:
secs]395416.818: [CMS395418.585: [CMS-concurrent-abortable-preclean: 4.327/44.770 secs]
(concurrent mode failure): 262144K->262143K(262144K), 14.1837441 secs]
863648K->375462K(969984K), 40.8324019 secs]
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms