I was seeing errors in 18 without escape analysis explicitly enabled. So unless it became enabled by default in 18, I don't think that was the issue.
-Todd On Tue, Apr 6, 2010 at 5:48 AM, Steve Loughran <ste...@apache.org> wrote: > > I know everyone has had bad experiences w/ Java 1.6.0_18 and was sticking > with JVM releases they trusted, but the set of security patches that have > come out with the _19 release change the situation. There are enough > server-side vulnerabilities there to make upgrading something to consider if > you are working with untrusted data. > > Has anyone tried the latest release at scale and got any good/bad > experiences to share? > > One interesting feature is it does actually disable Escape Analysis, which > I believe was one of the troublespots. When I start a JVM with the following > options > > -XX:+UseCompressedOops > -XX:+DoEscapeAnalysis > -XX:+UseParallelGC > -XX:+AggressiveOpts > > On > java version "1.6.0_19" > Java(TM) SE Runtime Environment (build 1.6.0_19-b04) > Java HotSpot(TM) 64-Bit Server VM (build 16.2-b04, mixed mode) > > I get told off: > > Java HotSpot(TM) 64-Bit Server VM warning: Escape Analysis is disabled in > this release. > > Was it Escape Analysis that was hurting people in the _18 version? > > -steve > > -- Todd Lipcon Software Engineer, Cloudera
