please load a jira entry if you want an update of 1.7 in solaris (I
will have a look tomorrow to upgrade that)
2013/1/30 Ted Dunning :
> This is an ancient JRE. The current series is 1.7.0_11 while the JRE in
> the stack trace mentioned here is from the original release. Many serious
> problems
This is an ancient JRE. The current series is 1.7.0_11 while the JRE in
the stack trace mentioned here is from the original release. Many serious
problems were noted in early Java 7 builds.
I seriously doubt that making a bug report against this version of the JDK
will be useful.
On the other h
when the core file here https://builds.apache.org/userContent/isis/
will be 554M transfer will be complete.
2013/1/30 Martin Desruisseaux :
> Hello build master
>
> We are still suffering from systematic JVM crashes when building Apache SIS
> on Jenkins. I don't think that this is the fault of ou
Hello build master
We are still suffering from systematic JVM crashes when building Apache
SIS on Jenkins. I don't think that this is the fault of our application
since we have no native code, only pure Java. The crash seems to occur
in java.util.zip.ZipFile code. According to the crash report
ilto:u...@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 t
che.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
>
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 Mav
