Thanks for tracking this down, guys.
Cheers,
Chris
On 2/28/13 1:48 AM, "Martin Desruisseaux"
wrote:
>Hello all
>
>Just for the record: as predicted by Jesse Glick, upgrading to latest
>JDK7 on Solaris didn't solved the JVM crash. So I tied the build of the
>JDK7 branch to the Ubuntu slaves as s
Hello all
Just for the record: as predicted by Jesse Glick, upgrading to latest
JDK7 on Solaris didn't solved the JVM crash. So I tied the build of the
JDK7 branch to the Ubuntu slaves as suggested by Gavin McDonald. After
Apache SIS release, we will use the released Maven "sis-build-helper"
Hello Gavin
Le 22/02/13 06:40, Gavin McDonald a écrit :
Ok, upgraded. Now solaris1 is as follows:
bash-3.00# /home/hudson/tools/java/latest1.7/bin/java -version
java version "1.7.0_15"
Java(TM) SE Runtime Environment (build 1.7.0_15-b03)
Java HotSpot(TM) Server VM (build 23.7-b01, mixed mode)
> -Original Message-
> From: Gavin McDonald [mailto:ga...@16degrees.com.au]
> Sent: Friday, 22 February 2013 1:45 PM
> To: builds@apache.org
> Subject: RE: Apache build infrastructure or Oracle JVM problem: crash in
> native JDK code
>
> I think we need to
)
I'll let you know when 'solaris1' is updated if you prefer to continue with
that.
HTH
Gav...
> -Original Message-
> From: Martin Desruisseaux [mailto:martin.desruisse...@geomatys.fr]
> Sent: Thursday, 21 February 2013 3:53 AM
> To: builds@apache.org
> S
Le 20/02/13 18:12, Jesse Glick a écrit :
I would merely claim that loading classes from a snapshot JAR is
_prone_ to triggering crashes when other factors come into play which
might be difficult to predict.
I agree. We will move to a non-snapshot version when we can. The only
issue is that we n
On 02/20/2013 11:46 AM, Martin Desruisseaux wrote:
clobbering an open JAR file is an hypothesis that may explain the JVM crash,
but this is unverified.
Indeed it is only a hypothesis, though one based on repeated encounters with similar crashes over the course of years of development that were
Hello Jesse
Le 20/02/13 16:20, Jesse Glick a écrit :
On 02/06/2013 01:39 PM, Jesse Glick wrote:
I could file a JIRA ticket for it
https://jira.codehaus.org/browse/MNG-5437
Thanks a lot for writing this JIRA task. However it may be worth to
emphases that clobbering an open JAR file is an hyp
On 02/06/2013 01:39 PM, Jesse Glick wrote:
I could file a JIRA ticket for it
https://jira.codehaus.org/browse/MNG-5437
Le 06/02/13 19:39, Jesse Glick a écrit :
On 02/06/2013 06:12 AM, Martin Desruisseaux wrote:
the approach that we wanted to apply has been used for more than 5
years on Windows, Solaris, Linux Gentoo, Linux Ubuntu, MacOS, and
other Hudson/Jenkins servers without any JVM crash
Perhaps you were ju
Thanks for this.
On Wed, Feb 6, 2013 at 10:39 AM, Jesse Glick wrote:
> To Ted Dunning’s request for the bug number—searching on bugs.sun.comseems to
> be broken, and as I no longer work for Oracle I cannot use the
> internal search tool. Fortunately I managed to dig it up using other means:
>
On 02/06/2013 06:12 AM, Martin Desruisseaux wrote:
the approach that we wanted to apply has been used for more than 5 years on
Windows, Solaris, Linux Gentoo, Linux Ubuntu, MacOS, and other Hudson/Jenkins
servers without any JVM crash
Perhaps you were just lucky, or perhaps there is something
Hello all, and thanks for the reply.
Le 06/02/13 02:49, Jesse Glick a écrit :
On 02/05/2013 07:30 PM, sebb wrote:
a pure Java application should not be able to cause a JVM crash
Depends entirely on what you mean by “pure Java application”. When you
have filesystem and Process access, you can d
Le 06/02/13 06:44, Ted Dunning a écrit :
This is still a very early version of java 7. It would be good to update
it.
That would be my preferred approach, if possible...
Thanks,
Martin
Do you have a reference to the bug?
This is still a very early version of java 7. It would be good to update
it.
On Tue, Feb 5, 2013 at 5:49 PM, Jesse Glick wrote:
> On 02/05/2013 07:30 PM, sebb wrote:
>
>> a pure Java application should not be able to cause a JVM crash
>>
>
> Depends entirely
On 6 February 2013 01:49, Jesse Glick wrote:
> On 02/05/2013 07:30 PM, sebb wrote:
>>
>> a pure Java application should not be able to cause a JVM crash
>
>
> Depends entirely on what you mean by “pure Java application”. When you have
> filesystem and Process access, you can do whatever the user s
On 02/05/2013 07:30 PM, sebb wrote:
a pure Java application should not be able to cause a JVM crash
Depends entirely on what you mean by “pure Java application”. When you have filesystem and Process access, you can do whatever the user shell account can do, which
certainly includes triggering
On 5 February 2013 17:59, Jesse Glick wrote:
> On 02/04/2013 09:23 AM, Martin Desruisseaux wrote:
>>
>> the crash occurs in the C/C++ implementation of
>> java.util.zip.ZipFile.getEntry(String)
>
>
> This is almost always a symptom of user error rather than a JDK bug; or at
> least any bug report
On 02/04/2013 09:23 AM, Martin Desruisseaux wrote:
the crash occurs in the C/C++ implementation of
java.util.zip.ZipFile.getEntry(String)
This is almost always a symptom of user error rather than a JDK bug; or at least any bug report to Oracle along these lines will be rejected. Something in y
No problem buddy!
To register, simply send an email to builds-subscr...@apache.org and
follow the instructions from there.
Still waiting to see what builds@ people decided though.
Thanks,
Chris
On 2/4/13 8:50 AM, "Martin Desruisseaux"
wrote:
>Hello Chris
>
>Le 04/02/13 17:21, Mattmann, Chris
Hello Chris
Le 04/02/13 17:21, Mattmann, Chris A (388J) a écrit :
There were some replies too — that centered around upgrading the JVM on that
machine to a newer version and seeing if that fixes the problem as you suggest.
Then this is my fault, I didn't saw those replies. It may be because
mailto:in...@apache.org>"
mailto:in...@apache.org>>
Subject: Re: Apache build infrastructure or Oracle JVM problem: crash in native
JDK code
Thanks for keeping on this, Martin. I will copy infra@ to see if they have any
insight in to this. Also, @mattmann may be able to lend a hand here t
22 matches
Mail list logo
