You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by Marshall Schor <ms...@schor.com> on 2011/09/07 21:24:35 UTC
getting some StreamCorruptedException failures
Some of our Jenkins builds are failing at various spots in our build, with this:
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ uimaj-test-util ---
[INFO] Building jar: <https://builds.apache.org/job/UIMA-SDK/ws/trunk/uimaj-test-util/target/uimaj-test-util-2.3.2-SNAPSHOT.jar>
Sep 7, 2011 7:01:58 PM hudson.remoting.Channel$ReaderThread run
SEVERE: I/O error in channel channel
java.io.StreamCorruptedException
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1332)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at hudson.remoting.Channel$ReaderThread.run(Channel.java:1031)
channel stopped
ERROR: Maven JVM terminated unexpectedly with exit code 0
Rerunning the build often succeeds, so it seems kind of random. You can see
the latest failure here:
https://builds.apache.org/job/UIMA-SDK/115/console
Any ideas of what we might be doing wrong, or is there some setup that we need
to fix?
-Marshall Schor
Re: getting some StreamCorruptedException failures
Posted by Andreas Veithen <an...@gmail.com>.
On Tue, Dec 27, 2011 at 15:31, Andreas Lehmkuehler <le...@apache.org> wrote:
> Hi,
>
> Am 27.12.2011 12:37, schrieb Andreas Veithen:
>
>> Did anybody ever find a solution for this? We are also seeing this
>> with our Axis2 and WS builds, but it seems to only affect ubuntu4 and
>> ubuntu5. After tying the builds to ubuntu1||ubuntu2||ubuntu3 they run
>> much more stable.
>
> We got the same issue with our build. Both crashed on ubuntu5, the following
> build 399 was successful on ubuntu4
Build #393 ran on ubuntu4 and failed with a StreamCorruptedException
as well. Note that the builds don't fail systematically on ubuntu4 and
5. It's about 1 out of 2 builds that fail.
> https://builds.apache.org/job/PDFBox-trunk/397/
> https://builds.apache.org/job/PDFBox-trunk/398/
>
>>
>> Andreas
>>
>
> BR
> Andreas Lehmkühler
>
>
>> On Wed, Sep 7, 2011 at 21:24, Marshall Schor<ms...@schor.com> wrote:
>>>
>>> Some of our Jenkins builds are failing at various spots in our build,
>>> with this:
>>>
>>> [JENKINS] Recording test results
>>> [INFO]
>>> [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ uimaj-test-util ---
>>> [INFO] Building
>>> jar:<https://builds.apache.org/job/UIMA-SDK/ws/trunk/uimaj-test-util/target/uimaj-test-util-2.3.2-SNAPSHOT.jar>
>>> Sep 7, 2011 7:01:58 PM hudson.remoting.Channel$ReaderThread run
>>> SEVERE: I/O error in channel channel
>>> java.io.StreamCorruptedException
>>> at
>>> java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1332)
>>> at
>>> java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
>>> at hudson.remoting.Channel$ReaderThread.run(Channel.java:1031)
>>> channel stopped
>>> ERROR: Maven JVM terminated unexpectedly with exit code 0
>>>
>>> Rerunning the build often succeeds, so it seems kind of random. You can
>>> see
>>> the latest failure here:
>>> https://builds.apache.org/job/UIMA-SDK/115/console
>>>
>>> Any ideas of what we might be doing wrong, or is there some setup that we
>>> need
>>> to fix?
>>>
>>> -Marshall Schor
>
>
Re: getting some StreamCorruptedException failures
Posted by Andreas Lehmkuehler <le...@apache.org>.
Hi,
Am 27.12.2011 12:37, schrieb Andreas Veithen:
> Did anybody ever find a solution for this? We are also seeing this
> with our Axis2 and WS builds, but it seems to only affect ubuntu4 and
> ubuntu5. After tying the builds to ubuntu1||ubuntu2||ubuntu3 they run
> much more stable.
We got the same issue with our build. Both crashed on ubuntu5, the following
build 399 was successful on ubuntu4
https://builds.apache.org/job/PDFBox-trunk/397/
https://builds.apache.org/job/PDFBox-trunk/398/
>
> Andreas
>
BR
Andreas Lehmkühler
> On Wed, Sep 7, 2011 at 21:24, Marshall Schor<ms...@schor.com> wrote:
>> Some of our Jenkins builds are failing at various spots in our build, with this:
>>
>> [JENKINS] Recording test results
>> [INFO]
>> [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ uimaj-test-util ---
>> [INFO] Building jar:<https://builds.apache.org/job/UIMA-SDK/ws/trunk/uimaj-test-util/target/uimaj-test-util-2.3.2-SNAPSHOT.jar>
>> Sep 7, 2011 7:01:58 PM hudson.remoting.Channel$ReaderThread run
>> SEVERE: I/O error in channel channel
>> java.io.StreamCorruptedException
>> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1332)
>> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
>> at hudson.remoting.Channel$ReaderThread.run(Channel.java:1031)
>> channel stopped
>> ERROR: Maven JVM terminated unexpectedly with exit code 0
>>
>> Rerunning the build often succeeds, so it seems kind of random. You can see
>> the latest failure here:
>> https://builds.apache.org/job/UIMA-SDK/115/console
>>
>> Any ideas of what we might be doing wrong, or is there some setup that we need
>> to fix?
>>
>> -Marshall Schor
Re: getting some StreamCorruptedException failures
Posted by Olivier Lamy <ol...@apache.org>.
2011/12/30 Niklas Gustavsson <ni...@protocol7.com>:
> On Fri, Dec 30, 2011 at 10:55 AM, Olivier Lamy <ol...@apache.org> wrote:
>> btw I have fixed that in jenkins code (will be released with 1.447 ).
>> As it break some builds if needed I can provide a SNAPSHOT build with
>> the fix until 1.447 is released.
>
> What's the timing on 1.447 and are there workarounds?
Normally around 2 weeks.
I have asked to have a faster release but no response yet.
And no real workaround.
>
> /niklas
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: getting some StreamCorruptedException failures
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Fri, Dec 30, 2011 at 10:55 AM, Olivier Lamy <ol...@apache.org> wrote:
> btw I have fixed that in jenkins code (will be released with 1.447 ).
> As it break some builds if needed I can provide a SNAPSHOT build with
> the fix until 1.447 is released.
What's the timing on 1.447 and are there workarounds?
/niklas
Re: getting some StreamCorruptedException failures
Posted by Andreas Veithen <an...@gmail.com>.
We are still getting StreamCorruptedExceptions, even after the upgrade. Example:
https://builds.apache.org/job/sandesha2-trunk/587/
Andreas
On Fri, Dec 30, 2011 at 17:21, Niklas Gustavsson <ni...@protocol7.com> wrote:
> On Fri, Dec 30, 2011 at 4:45 PM, Andreas Veithen
> <an...@gmail.com> wrote:
>> In our case, switching to Maven 2.2.1 is a valid workaround, so we
>> don't really care.
>>
>> On the other hand, I guess that many people are annoyed by the issues
>> that pop up after upgrading to a new Jenkins release (this seems to be
>> a somewhat recurring issue at the ASF). Therefore it may be a good
>> idea to install a SNAPSHOT and check for other issues that we may
>> identify (and if necessary repeat that in several iterations), so that
>> we eventually get a stable release that works well at the ASF and that
>> we can keep for a couple of months. WDYT?
>
> That was what we did with the former release. We ran that for like two
> months or so, but eventually problems like that with
> StreamCorruptedException creeps up. I guess that's the curse of having
> a large installation with many different types of builds.
>
> /niklas
Re: getting some StreamCorruptedException failures
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Fri, Dec 30, 2011 at 4:45 PM, Andreas Veithen
<an...@gmail.com> wrote:
> In our case, switching to Maven 2.2.1 is a valid workaround, so we
> don't really care.
>
> On the other hand, I guess that many people are annoyed by the issues
> that pop up after upgrading to a new Jenkins release (this seems to be
> a somewhat recurring issue at the ASF). Therefore it may be a good
> idea to install a SNAPSHOT and check for other issues that we may
> identify (and if necessary repeat that in several iterations), so that
> we eventually get a stable release that works well at the ASF and that
> we can keep for a couple of months. WDYT?
That was what we did with the former release. We ran that for like two
months or so, but eventually problems like that with
StreamCorruptedException creeps up. I guess that's the curse of having
a large installation with many different types of builds.
/niklas
Re: getting some StreamCorruptedException failures
Posted by Andreas Veithen <an...@gmail.com>.
In our case, switching to Maven 2.2.1 is a valid workaround, so we
don't really care.
On the other hand, I guess that many people are annoyed by the issues
that pop up after upgrading to a new Jenkins release (this seems to be
a somewhat recurring issue at the ASF). Therefore it may be a good
idea to install a SNAPSHOT and check for other issues that we may
identify (and if necessary repeat that in several iterations), so that
we eventually get a stable release that works well at the ASF and that
we can keep for a couple of months. WDYT?
Andreas
On Fri, Dec 30, 2011 at 10:55, Olivier Lamy <ol...@apache.org> wrote:
> Hello,
>
> btw I have fixed that in jenkins code (will be released with 1.447 ).
> As it break some builds if needed I can provide a SNAPSHOT build with
> the fix until 1.447 is released.
>
> Let me know.
>
> 2011/12/29 Olivier Lamy <ol...@apache.org>:
>> Looks to be an issue with mojo which fork lifecycle in jenkins listener.
>>
>> You are probably using sources plugin and goal jar.
>> Can you change and use jar-no-fork goal instead of jar ?
>>
>>
>> 2011/12/29 Andreas Veithen <an...@gmail.com>:
>>> Here is one example:
>>>
>>> https://builds.apache.org/view/A-F/view/Axis2/job/sandesha2-1.6/110/
>>>
>>> Note that after that failure I switched the build to Maven 2.2.1,
>>> which is why #111 completed successfully.
>>>
>>> Andreas
>>>
>>> On Thu, Dec 29, 2011 at 21:28, Olivier Lamy <ol...@apache.org> wrote:
>>>> Hello,
>>>> Looks to be a Jenkins issue here.
>>>> Can you give me the link to the build which generate that ?
>>>>
>>>> 2011/12/29 Andreas Veithen <an...@gmail.com>:
>>>>> On Thu, Dec 29, 2011 at 16:08, Niklas Gustavsson <ni...@protocol7.com> wrote:
>>>>>> On Thu, Dec 29, 2011 at 1:44 PM, Andreas Veithen
>>>>>> <an...@gmail.com> wrote:
>>>>>>> OK, thanks. Let me know when the upgrade is done. I will then switch a
>>>>>>> couple of builds back to Ubuntu (instead of ubuntu1||ubuntu2||ubuntu3)
>>>>>>> to check if that solves the issue.
>>>>>>
>>>>>> Done.
>>>>>>
>>>>>> /niklas
>>>>>
>>>>> Now I'm getting another failure:
>>>>>
>>>>> org.apache.maven.InternalErrorException: Internal error:
>>>>> java.lang.NullPointerException
>>>>> at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
>>>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
>>>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>>>> at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>> at java.lang.reflect.Method.invoke(Method.java:592)
>>>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
>>>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
>>>>> at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
>>>>> at hudson.maven.Maven3Builder.call(Maven3Builder.java:112)
>>>>> at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
>>>>> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
>>>>> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
>>>>> at hudson.remoting.Request$2.run(Request.java:287)
>>>>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
>>>>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
>>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
>>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
>>>>> at java.lang.Thread.run(Thread.java:595)
>>>>> Caused by: java.lang.NullPointerException
>>>>> at hudson.maven.ExecutedMojo.getMojoClass(ExecutedMojo.java:114)
>>>>> at hudson.maven.ExecutedMojo.<init>(ExecutedMojo.java:99)
>>>>> at hudson.maven.Maven3Builder$MavenExecutionListener.recordExecutionTime(Maven3Builder.java:524)
>>>>> at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:493)
>>>>> at hudson.maven.Maven3Builder$MavenExecutionListener.forkSucceeded(Maven3Builder.java:601)
>>>>> at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:97)
>>>>> at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:383)
>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>>>> ... 24 more
>>>>>
>>>>> The first two failures actually occurred in two different builds at
>>>>> the following times:
>>>>>
>>>>> Thu Dec 29 13:31:31 UTC 2011
>>>>> Thu Dec 29 13:32:01 UTC 2011
>>>>>
>>>>> This may actually be before the upgrade. It also looks like this
>>>>> affects Maven 3.0.3, but not Maven 2.2.1.
>>>>>
>>>>> Andreas
>>>>
>>>>
>>>>
>>>> --
>>>> Olivier Lamy
>>>> Talend: http://coders.talend.com
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: getting some StreamCorruptedException failures
Posted by Olivier Lamy <ol...@apache.org>.
Hello,
btw I have fixed that in jenkins code (will be released with 1.447 ).
As it break some builds if needed I can provide a SNAPSHOT build with
the fix until 1.447 is released.
Let me know.
2011/12/29 Olivier Lamy <ol...@apache.org>:
> Looks to be an issue with mojo which fork lifecycle in jenkins listener.
>
> You are probably using sources plugin and goal jar.
> Can you change and use jar-no-fork goal instead of jar ?
>
>
> 2011/12/29 Andreas Veithen <an...@gmail.com>:
>> Here is one example:
>>
>> https://builds.apache.org/view/A-F/view/Axis2/job/sandesha2-1.6/110/
>>
>> Note that after that failure I switched the build to Maven 2.2.1,
>> which is why #111 completed successfully.
>>
>> Andreas
>>
>> On Thu, Dec 29, 2011 at 21:28, Olivier Lamy <ol...@apache.org> wrote:
>>> Hello,
>>> Looks to be a Jenkins issue here.
>>> Can you give me the link to the build which generate that ?
>>>
>>> 2011/12/29 Andreas Veithen <an...@gmail.com>:
>>>> On Thu, Dec 29, 2011 at 16:08, Niklas Gustavsson <ni...@protocol7.com> wrote:
>>>>> On Thu, Dec 29, 2011 at 1:44 PM, Andreas Veithen
>>>>> <an...@gmail.com> wrote:
>>>>>> OK, thanks. Let me know when the upgrade is done. I will then switch a
>>>>>> couple of builds back to Ubuntu (instead of ubuntu1||ubuntu2||ubuntu3)
>>>>>> to check if that solves the issue.
>>>>>
>>>>> Done.
>>>>>
>>>>> /niklas
>>>>
>>>> Now I'm getting another failure:
>>>>
>>>> org.apache.maven.InternalErrorException: Internal error:
>>>> java.lang.NullPointerException
>>>> at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
>>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
>>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>>> at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:592)
>>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
>>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
>>>> at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
>>>> at hudson.maven.Maven3Builder.call(Maven3Builder.java:112)
>>>> at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
>>>> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
>>>> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
>>>> at hudson.remoting.Request$2.run(Request.java:287)
>>>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
>>>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
>>>> at java.lang.Thread.run(Thread.java:595)
>>>> Caused by: java.lang.NullPointerException
>>>> at hudson.maven.ExecutedMojo.getMojoClass(ExecutedMojo.java:114)
>>>> at hudson.maven.ExecutedMojo.<init>(ExecutedMojo.java:99)
>>>> at hudson.maven.Maven3Builder$MavenExecutionListener.recordExecutionTime(Maven3Builder.java:524)
>>>> at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:493)
>>>> at hudson.maven.Maven3Builder$MavenExecutionListener.forkSucceeded(Maven3Builder.java:601)
>>>> at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:97)
>>>> at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:383)
>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>>> ... 24 more
>>>>
>>>> The first two failures actually occurred in two different builds at
>>>> the following times:
>>>>
>>>> Thu Dec 29 13:31:31 UTC 2011
>>>> Thu Dec 29 13:32:01 UTC 2011
>>>>
>>>> This may actually be before the upgrade. It also looks like this
>>>> affects Maven 3.0.3, but not Maven 2.2.1.
>>>>
>>>> Andreas
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: getting some StreamCorruptedException failures
Posted by Olivier Lamy <ol...@apache.org>.
Looks to be an issue with mojo which fork lifecycle in jenkins listener.
You are probably using sources plugin and goal jar.
Can you change and use jar-no-fork goal instead of jar ?
2011/12/29 Andreas Veithen <an...@gmail.com>:
> Here is one example:
>
> https://builds.apache.org/view/A-F/view/Axis2/job/sandesha2-1.6/110/
>
> Note that after that failure I switched the build to Maven 2.2.1,
> which is why #111 completed successfully.
>
> Andreas
>
> On Thu, Dec 29, 2011 at 21:28, Olivier Lamy <ol...@apache.org> wrote:
>> Hello,
>> Looks to be a Jenkins issue here.
>> Can you give me the link to the build which generate that ?
>>
>> 2011/12/29 Andreas Veithen <an...@gmail.com>:
>>> On Thu, Dec 29, 2011 at 16:08, Niklas Gustavsson <ni...@protocol7.com> wrote:
>>>> On Thu, Dec 29, 2011 at 1:44 PM, Andreas Veithen
>>>> <an...@gmail.com> wrote:
>>>>> OK, thanks. Let me know when the upgrade is done. I will then switch a
>>>>> couple of builds back to Ubuntu (instead of ubuntu1||ubuntu2||ubuntu3)
>>>>> to check if that solves the issue.
>>>>
>>>> Done.
>>>>
>>>> /niklas
>>>
>>> Now I'm getting another failure:
>>>
>>> org.apache.maven.InternalErrorException: Internal error:
>>> java.lang.NullPointerException
>>> at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>> at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:592)
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
>>> at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
>>> at hudson.maven.Maven3Builder.call(Maven3Builder.java:112)
>>> at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
>>> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
>>> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
>>> at hudson.remoting.Request$2.run(Request.java:287)
>>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
>>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
>>> at java.lang.Thread.run(Thread.java:595)
>>> Caused by: java.lang.NullPointerException
>>> at hudson.maven.ExecutedMojo.getMojoClass(ExecutedMojo.java:114)
>>> at hudson.maven.ExecutedMojo.<init>(ExecutedMojo.java:99)
>>> at hudson.maven.Maven3Builder$MavenExecutionListener.recordExecutionTime(Maven3Builder.java:524)
>>> at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:493)
>>> at hudson.maven.Maven3Builder$MavenExecutionListener.forkSucceeded(Maven3Builder.java:601)
>>> at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:97)
>>> at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:383)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> ... 24 more
>>>
>>> The first two failures actually occurred in two different builds at
>>> the following times:
>>>
>>> Thu Dec 29 13:31:31 UTC 2011
>>> Thu Dec 29 13:32:01 UTC 2011
>>>
>>> This may actually be before the upgrade. It also looks like this
>>> affects Maven 3.0.3, but not Maven 2.2.1.
>>>
>>> Andreas
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: getting some StreamCorruptedException failures
Posted by Andreas Veithen <an...@gmail.com>.
Here is one example:
https://builds.apache.org/view/A-F/view/Axis2/job/sandesha2-1.6/110/
Note that after that failure I switched the build to Maven 2.2.1,
which is why #111 completed successfully.
Andreas
On Thu, Dec 29, 2011 at 21:28, Olivier Lamy <ol...@apache.org> wrote:
> Hello,
> Looks to be a Jenkins issue here.
> Can you give me the link to the build which generate that ?
>
> 2011/12/29 Andreas Veithen <an...@gmail.com>:
>> On Thu, Dec 29, 2011 at 16:08, Niklas Gustavsson <ni...@protocol7.com> wrote:
>>> On Thu, Dec 29, 2011 at 1:44 PM, Andreas Veithen
>>> <an...@gmail.com> wrote:
>>>> OK, thanks. Let me know when the upgrade is done. I will then switch a
>>>> couple of builds back to Ubuntu (instead of ubuntu1||ubuntu2||ubuntu3)
>>>> to check if that solves the issue.
>>>
>>> Done.
>>>
>>> /niklas
>>
>> Now I'm getting another failure:
>>
>> org.apache.maven.InternalErrorException: Internal error:
>> java.lang.NullPointerException
>> at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>> at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:592)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
>> at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
>> at hudson.maven.Maven3Builder.call(Maven3Builder.java:112)
>> at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
>> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
>> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
>> at hudson.remoting.Request$2.run(Request.java:287)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
>> at java.lang.Thread.run(Thread.java:595)
>> Caused by: java.lang.NullPointerException
>> at hudson.maven.ExecutedMojo.getMojoClass(ExecutedMojo.java:114)
>> at hudson.maven.ExecutedMojo.<init>(ExecutedMojo.java:99)
>> at hudson.maven.Maven3Builder$MavenExecutionListener.recordExecutionTime(Maven3Builder.java:524)
>> at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:493)
>> at hudson.maven.Maven3Builder$MavenExecutionListener.forkSucceeded(Maven3Builder.java:601)
>> at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:97)
>> at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:383)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>> ... 24 more
>>
>> The first two failures actually occurred in two different builds at
>> the following times:
>>
>> Thu Dec 29 13:31:31 UTC 2011
>> Thu Dec 29 13:32:01 UTC 2011
>>
>> This may actually be before the upgrade. It also looks like this
>> affects Maven 3.0.3, but not Maven 2.2.1.
>>
>> Andreas
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: getting some StreamCorruptedException failures
Posted by Olivier Lamy <ol...@apache.org>.
Hello,
Looks to be a Jenkins issue here.
Can you give me the link to the build which generate that ?
2011/12/29 Andreas Veithen <an...@gmail.com>:
> On Thu, Dec 29, 2011 at 16:08, Niklas Gustavsson <ni...@protocol7.com> wrote:
>> On Thu, Dec 29, 2011 at 1:44 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>>> OK, thanks. Let me know when the upgrade is done. I will then switch a
>>> couple of builds back to Ubuntu (instead of ubuntu1||ubuntu2||ubuntu3)
>>> to check if that solves the issue.
>>
>> Done.
>>
>> /niklas
>
> Now I'm getting another failure:
>
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.NullPointerException
> at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:592)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
> at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:112)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:287)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.NullPointerException
> at hudson.maven.ExecutedMojo.getMojoClass(ExecutedMojo.java:114)
> at hudson.maven.ExecutedMojo.<init>(ExecutedMojo.java:99)
> at hudson.maven.Maven3Builder$MavenExecutionListener.recordExecutionTime(Maven3Builder.java:524)
> at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:493)
> at hudson.maven.Maven3Builder$MavenExecutionListener.forkSucceeded(Maven3Builder.java:601)
> at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:97)
> at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
> at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:383)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> ... 24 more
>
> The first two failures actually occurred in two different builds at
> the following times:
>
> Thu Dec 29 13:31:31 UTC 2011
> Thu Dec 29 13:32:01 UTC 2011
>
> This may actually be before the upgrade. It also looks like this
> affects Maven 3.0.3, but not Maven 2.2.1.
>
> Andreas
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: getting some StreamCorruptedException failures
Posted by Andreas Veithen <an...@gmail.com>.
On Thu, Dec 29, 2011 at 16:08, Niklas Gustavsson <ni...@protocol7.com> wrote:
> On Thu, Dec 29, 2011 at 1:44 PM, Andreas Veithen
> <an...@gmail.com> wrote:
>> OK, thanks. Let me know when the upgrade is done. I will then switch a
>> couple of builds back to Ubuntu (instead of ubuntu1||ubuntu2||ubuntu3)
>> to check if that solves the issue.
>
> Done.
>
> /niklas
Now I'm getting another failure:
org.apache.maven.InternalErrorException: Internal error:
java.lang.NullPointerException
at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:112)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at hudson.maven.ExecutedMojo.getMojoClass(ExecutedMojo.java:114)
at hudson.maven.ExecutedMojo.<init>(ExecutedMojo.java:99)
at hudson.maven.Maven3Builder$MavenExecutionListener.recordExecutionTime(Maven3Builder.java:524)
at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:493)
at hudson.maven.Maven3Builder$MavenExecutionListener.forkSucceeded(Maven3Builder.java:601)
at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:97)
at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:383)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
... 24 more
The first two failures actually occurred in two different builds at
the following times:
Thu Dec 29 13:31:31 UTC 2011
Thu Dec 29 13:32:01 UTC 2011
This may actually be before the upgrade. It also looks like this
affects Maven 3.0.3, but not Maven 2.2.1.
Andreas
Re: getting some StreamCorruptedException failures
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Thu, Dec 29, 2011 at 1:44 PM, Andreas Veithen
<an...@gmail.com> wrote:
> OK, thanks. Let me know when the upgrade is done. I will then switch a
> couple of builds back to Ubuntu (instead of ubuntu1||ubuntu2||ubuntu3)
> to check if that solves the issue.
Done.
/niklas
Re: getting some StreamCorruptedException failures
Posted by Andreas Veithen <an...@gmail.com>.
On Thu, Dec 29, 2011 at 12:48, Niklas Gustavsson <ni...@protocol7.com> wrote:
> On Thu, Dec 29, 2011 at 9:55 AM, Andreas Veithen
> <an...@gmail.com> wrote:
>> On Wed, Dec 28, 2011 at 14:52, Niklas Gustavsson <ni...@protocol7.com> wrote:
>>> On Tue, Dec 27, 2011 at 12:37 PM, Andreas Veithen
>>> <an...@gmail.com> wrote:
>>>> Did anybody ever find a solution for this? We are also seeing this
>>>> with our Axis2 and WS builds, but it seems to only affect ubuntu4 and
>>>> ubuntu5. After tying the builds to ubuntu1||ubuntu2||ubuntu3 they run
>>>> much more stable.
>>>
>>> I've cleaned up a lot of dead processes on ubuntu5, let's see if that
>>> help any. Will do the same on the other nodes when they are offline.
>>>
>>> /niklas
>>
>> Less than an hour after your mail, another build failed with the same
>> error on ubuntu5 again:
>>
>> https://builds.apache.org/job/sandesha2-1.6/108/
>
> Seems like this might be fixed, I'll try an upgrade.
>
> https://issues.jenkins-ci.org/browse/JENKINS-8856
>
> /niklas
OK, thanks. Let me know when the upgrade is done. I will then switch a
couple of builds back to Ubuntu (instead of ubuntu1||ubuntu2||ubuntu3)
to check if that solves the issue.
Andreas
Re: getting some StreamCorruptedException failures
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Thu, Dec 29, 2011 at 9:55 AM, Andreas Veithen
<an...@gmail.com> wrote:
> On Wed, Dec 28, 2011 at 14:52, Niklas Gustavsson <ni...@protocol7.com> wrote:
>> On Tue, Dec 27, 2011 at 12:37 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>>> Did anybody ever find a solution for this? We are also seeing this
>>> with our Axis2 and WS builds, but it seems to only affect ubuntu4 and
>>> ubuntu5. After tying the builds to ubuntu1||ubuntu2||ubuntu3 they run
>>> much more stable.
>>
>> I've cleaned up a lot of dead processes on ubuntu5, let's see if that
>> help any. Will do the same on the other nodes when they are offline.
>>
>> /niklas
>
> Less than an hour after your mail, another build failed with the same
> error on ubuntu5 again:
>
> https://builds.apache.org/job/sandesha2-1.6/108/
Seems like this might be fixed, I'll try an upgrade.
https://issues.jenkins-ci.org/browse/JENKINS-8856
/niklas
Re: getting some StreamCorruptedException failures
Posted by Andreas Veithen <an...@gmail.com>.
On Wed, Dec 28, 2011 at 14:52, Niklas Gustavsson <ni...@protocol7.com> wrote:
> On Tue, Dec 27, 2011 at 12:37 PM, Andreas Veithen
> <an...@gmail.com> wrote:
>> Did anybody ever find a solution for this? We are also seeing this
>> with our Axis2 and WS builds, but it seems to only affect ubuntu4 and
>> ubuntu5. After tying the builds to ubuntu1||ubuntu2||ubuntu3 they run
>> much more stable.
>
> I've cleaned up a lot of dead processes on ubuntu5, let's see if that
> help any. Will do the same on the other nodes when they are offline.
>
> /niklas
Less than an hour after your mail, another build failed with the same
error on ubuntu5 again:
https://builds.apache.org/job/sandesha2-1.6/108/
Probably the dead processes are a consequence of the issue, and not
the root cause.
Andreas
Re: getting some StreamCorruptedException failures
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Tue, Dec 27, 2011 at 12:37 PM, Andreas Veithen
<an...@gmail.com> wrote:
> Did anybody ever find a solution for this? We are also seeing this
> with our Axis2 and WS builds, but it seems to only affect ubuntu4 and
> ubuntu5. After tying the builds to ubuntu1||ubuntu2||ubuntu3 they run
> much more stable.
I've cleaned up a lot of dead processes on ubuntu5, let's see if that
help any. Will do the same on the other nodes when they are offline.
/niklas
Re: getting some StreamCorruptedException failures
Posted by Andreas Veithen <an...@gmail.com>.
Did anybody ever find a solution for this? We are also seeing this
with our Axis2 and WS builds, but it seems to only affect ubuntu4 and
ubuntu5. After tying the builds to ubuntu1||ubuntu2||ubuntu3 they run
much more stable.
Andreas
On Wed, Sep 7, 2011 at 21:24, Marshall Schor <ms...@schor.com> wrote:
> Some of our Jenkins builds are failing at various spots in our build, with this:
>
> [JENKINS] Recording test results
> [INFO]
> [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ uimaj-test-util ---
> [INFO] Building jar: <https://builds.apache.org/job/UIMA-SDK/ws/trunk/uimaj-test-util/target/uimaj-test-util-2.3.2-SNAPSHOT.jar>
> Sep 7, 2011 7:01:58 PM hudson.remoting.Channel$ReaderThread run
> SEVERE: I/O error in channel channel
> java.io.StreamCorruptedException
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1332)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
> at hudson.remoting.Channel$ReaderThread.run(Channel.java:1031)
> channel stopped
> ERROR: Maven JVM terminated unexpectedly with exit code 0
>
> Rerunning the build often succeeds, so it seems kind of random. You can see
> the latest failure here:
> https://builds.apache.org/job/UIMA-SDK/115/console
>
> Any ideas of what we might be doing wrong, or is there some setup that we need
> to fix?
>
> -Marshall Schor