[JIRA] Commented: (JENKINS-7809) Remote Launcher randomly returns no data.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (JENKINS-7809) Remote Launcher randomly returns no data.

JIRA noreply@jenkins-ci.org

    [ http://issues.jenkins-ci.org/browse/JENKINS-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145824#comment-145824 ]

Kohsuke Kawaguchi commented on JENKINS-7809:
--------------------------------------------

I wonder if this was a different manifestation of JENKINS-7745, which we fixed in 1.397. I encourage people to upgrade to 1.397 and report their results.

> Remote Launcher randomly returns no data.
> -----------------------------------------
>
>                 Key: JENKINS-7809
>                 URL: http://issues.jenkins-ci.org/browse/JENKINS-7809
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>         Environment: Hudson 1.378-1.383
>            Reporter: Rob Petti
>            Assignee: Kohsuke Kawaguchi
>            Priority: Blocker
>
> Since 1.378, the remoting functions of hudson have become unstable. When using a Launcher to execute commands remotely on a slave, sometimes it fails to return any data. The following stack trace is found in the hudson log when this occurs.
> {code}
> Oct 15, 2010 10:12:17 AM hudson.remoting.ProxyOutputStream$Chunk$1 run
> WARNING: Failed to write to stream
> java.io.IOException: Pipe closed
>         at java.io.PipedInputStream.checkStateForReceive(PipedInputStream.java:244)
>         at java.io.PipedInputStream.receive(PipedInputStream.java:210)
>         at java.io.PipedOutputStream.write(PipedOutputStream.java:132)
>         at java.io.OutputStream.write(OutputStream.java:58)
>         at hudson.util.DelegatingOutputStream.write(DelegatingOutputStream.java:51)
>         at hudson.remoting.ProxyOutputStream$Chunk$1.run(ProxyOutputStream.java:185)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:619)
> {code}
> This is currently causing issues with the perforce plugin (JENKINS-7664), and I've been able to reproduce it using the hudson_main_trunk#331 build on ci.hudson-labs.org as well.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira