Hi Mark, I haven't seen this personally yet. BTW, Sun hasn't replied to my bug report submission. I don't know if it has been discarded or simply delayed... Maybe you should try to submit a report yourself, it might have a better fortune...
Best regards, Jerome _____ De : Mark Derricutt [mailto:[EMAIL PROTECTED] Envoyé : lundi 21 juillet 2008 06:13 À : [email protected] Objet : Re: Restlet causing JVM crashes Hey all, This problem's just started to hit again on our production boxes running RHEl 3 and RHEL 5 and JDK 1.6_06. I tried checking what Kevin changed (volatile to final) but can't see any volatile's mentioned in HeaderReader class (but my pretty much everywhere else). It can't be just us and Kevin seeing this can it? We're now seeing it locally across multiple VM versions. Mark On Tue, Jun 10, 2008 at 12:12 AM, Kevin Conaway <[EMAIL PROTECTED]> wrote: Hi Mark, I had the same problem as you. I tweaked some lines of code in that class and recompiled and the issue went away. It feels like a bug in the JVM because the error is happening when Hotspot decides to recompile the class. I never did figure out what was causing it. I had posted to [EMAIL PROTECTED] back in April: http://restlet.tigris.org/servlets/ReadMsg?list=code <http://restlet.tigris.org/servlets/ReadMsg?list=code&msgNo=139> &msgNo=139 Kevin On Wed, Jun 4, 2008 at 12:37 AM, Rob Heittman <[EMAIL PROTECTED]> wrote: That's a new one on me, but Hardy has been the locus of a bunch of new JVM crash issues, mainly with Athlon processors. Also there have been some similar issues with 64-bit under Red Hat and Fedora. This is the Sun JVM I get installing sun-java6-jdk from multiverse, and I don't get JVM crashes on P4, Centrino, or Core Duo. java version "1.6.0_06" Java(TM) SE Runtime Environment (build 1.6.0_06-b02) Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode, sharing) Where did you get yours from? Direct Sun download? Hardy tries very hard to use OpenJDK, which also doesn't crash for me on P4, Centrino, or Core Duo. - Rob -- "It is easier to optimize correct code than to correct optimized code." -- Bill Harlan
