R27.6 does not respect -Xgc:gencon
650138Jul 15 2008 — edited Feb 3 2009Hi all,
Yesterday (14/7/2008) we upgrade to JRRT-3.0.3 because had serious crash problems with R27.3 lately. On a production machine, mind you!
To our surprise we notice that, having only changed the JVM and nothing more to our setup, that despite passing -Xgc:gencon as a parameter we now find the following output in our logs:
[...]
[INFO ][memory ] 237.002: parallel nursery GC 2198359K->2117511K (2359296K), 519.888 ms
[INFO ][memory ] 244.604: parallel nursery GC 2315890K->2169186K (2359296K), 157.788 ms
[INFO ][memory ] 247.780: parallel nursery GC 2353358K->2359296K (2359296K), 183.088 ms
[INFO ][memory ] Changing GC strategy to Generational Concurrent Mark, Parallel Sweep <- ?!
[INFO ][memory ] 247.967-250.979: GC 2359296K->297234K (2359296K), sum of pauses 1098.771 ms
[INFO ][memory ] 356.007: parallel nursery GC 683361K->537549K (2359296K), 161.786 ms
[...]
[INFO ][memory ] 5266.257: parallel nursery GC 1725672K->1579713K (2359296K), 385.391 ms
[INFO ][memory ] 5754.453: parallel nursery GC 1847014K->1701158K (2359296K), 1200.084 ms
[INFO ][memory ] 6664.898: parallel nursery GC 1846958K->1701158K (2359296K), 454.978 ms
[INFO ][memory ] 7274.429: parallel nursery GC 1846958K->1700902K (2359296K), 203.386 ms
[INFO ][memory ] 8070.782: parallel nursery GC 1899202K->1753073K (2359296K), 416.967 ms
[INFO ][memory ] 8987.941: parallel nursery GC 1989611K->1843758K (2359296K), 157.430 ms
[INFO ][memory ] 9236.093: parallel nursery GC 2027047K->1881119K (2359296K), 224.879 ms
[INFO ][memory ] 9323.686: parallel nursery GC 2060315K->1914515K (2359296K), 158.513 ms
[INFO ][memory ] Changing GC strategy to Generational Concurrent Mark & Sweep
[INFO ][memory ] 9644.149-9647.129: GC 2054132K->324792K (2359296K), sum of pauses 1160.854 ms
[INFO ][memory ] 9859.229: parallel nursery GC 726029K->579545K (2359296K), 142.107 ms
[...]
Below the VM params as reported by jconsole:
-Xms2304m -Xmx2304m -XnoOpt -Dfile.encoding=ISO-8859-15 -Xgc:gencon -Xns:192m -da -Duser.timezone=Europe/Brussels -Dweblogic.alternateTypesDirectory=./lib -Djrockit.codegen.strcmp.enabled=0 -Djava.awt.headless=true -Dj2ee.config=/bea/user_projects/domains/azvub/config/j2ee.config -DTRANS=prod -Dcom.sun.management.jmxremote.port=17031 -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -verbose:gc -XnoOpt -Dplatform.home=/bea/install/wlserver_10.0 -Dwls.home=/bea/install/wlserver_10.0/server -Dweblogic.home=/bea/install/wlserver_10.0/server -Dwli.home=/bea/install/wlserver_10.0/integration -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/bea/install/patch_wls1000/profiles/default/sysext_manifest_classpath -Dweblogic.Name=myserver -Djava.security.policy=/bea/install/wlserver_10.0/server/lib/weblogic.policy -Dsun.java.launcher=SUN_STANDARD
Similarly we had to use -XnoOpt in the past (unstable, crashes with jconn3 driver). This options seem to be ignored too. It apparently it is -Xnoopt on the M$ port. Was it always like that because it really worked on our Sun boxes till yesterday.
Did something change in the -X params (unannounced as clearly stated in the docs).
If anyone can give some info here it would be much appreciated.
Best regards,
Johan