www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler" <...@thetaphi.de>
Subject RE: Systematic JVM crash on Jenkins
Date Tue, 22 Jan 2013 06:00:20 GMT
Hi again,

As described in my previous mail, I would open an JIRA issue to request update of JDK 7 on
the Solaris node! This bug can be caused by the wrong loop compilation of the Hotspot compiler
(e.g. produces invlid pointer, then used by the bundled native zlib library or similar). If
this issue does not fix with latest 7 update, I would open bug report. Can you reproduce this
also on another machine?

Uwe

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de


> -----Original Message-----
> From: Uwe Schindler [mailto:uwe@thetaphi.de]
> Sent: Tuesday, January 22, 2013 6:27 AM
> To: builds@apache.org
> Subject: RE: Systematic JVM crash on Jenkins
> 
> Hi,
> 
> Java 7.0-b147 is the original Java 7 GA release without any updates. You might
> remember  the bug, the Apache Lucene developers found in this version [1],
> causing e.g. SIGSEGV on startup of Apache Solr or corrupting indexes. I would
> strongly recommend to *not* use this version and update to 7u1 [2] or later!
> Of course without more details I cannot see if this is also the same bug, but in
> general the GA release is unuseable in production systems.
> 
> Uwe
> 
> [1] http://blog.thetaphi.de/2011/07/real-story-behind-java-7-ga-bugs.html
> [2] http://blog.thetaphi.de/2011/10/java-7-update-1-released-does-it-
> fix.html
> 
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
> 
> 
> > -----Original Message-----
> > From: Martin Desruisseaux [mailto:martin.desruisseaux@geomatys.fr]
> > Sent: Tuesday, January 22, 2013 1:21 AM
> > To: builds@apache.org
> > Cc: Apache SIS
> > Subject: Systematic JVM crash on Jenkins
> >
> > Hello all
> >
> > The JDK7 branch of the SIS project is suffering from a systematic JVM
> > crash at building time on Jenkins. A look at the report file suggests
> > that the crash occurs in the call to the
> > java.util.zip.ZipFile.getEntry(String) method. We can workaround the
> > problem by disabling a custom Maven plugin. But a fix would of course
> > be preferred. Should I post a bug report on http://bugreport.sun.com,
> > or is there any other action that could be taken?
> >
> > The Jenkins job suffering from this crash is
> > https://builds.apache.org/job/sis-jdk7/. Below is the crash report:
> >
> > #
> > # A fatal error has been detected by the Java Runtime Environment:
> > #
> > #  SIGSEGV (0xb) at pc=0xfee952d6, pid=4889, tid=20 # # JRE version:
> > 7.0-b147 # Java VM: Java HotSpot(TM) Server VM (21.0-b17 mixed mode
> > solaris-x86 ) # Problematic frame:
> > # C  [libc.so.1+0x252d6]  memcpy+0x166 # # Core dump written. Default
> > location:
> > /zonestorage/hudson_solaris/home/hudson/hudson-
> slave/workspace/sis-
> > jdk7/core or core.4889
> > #
> > # An error report file with more information is saved as:
> > # /zonestorage/hudson_solaris/home/hudson/hudson-
> > slave/workspace/sis-jdk7/hs_err_pid4889.log
> > #
> > # If you would like to submit a bug report, please visit:
> > #http://bugreport.sun.com/bugreport/crash.jsp
> > # The crash happened outside the Java Virtual Machine in native code.
> > # See problematic frame for where to report the bug.
> > #
> >
> >
> > Thanks,
> >
> >      Martin



Mime
View raw message