EOFException on slave disconnect

[Ivo]

Hi,

I'm creating a cloud plugin and keep running into the following stacktrace on slave disconnect/termination:

WARNING: Computer.threadPoolForRemoting [#8] for 18392a20986e8 terminated
java.io.EOFException
        at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:613)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
        at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

I can not figure out why this is happening. I'm calling Jenkins.getInstance().removeNode in my _terminate method. Is there anything else I need to explicitly close/disconnect? The slave is automatically connected through jnlp.

Hopefully someone is able to help me out with this. I can provide additional code details if necessary.

Regards,

Ivo

[Kanstantsin Shautsou]

AFAIR it only warning and you could ignore it.

[Jesse Glick]

On Sun, Mar 20, 2016 at 12:01 PM, Kanstantsin Shautsou
<kanstan...@gmail.com> wrote:
> AFAIR it only warning and you could ignore it.

Yes, I think it is a bug in Remoting, probably not your fault.

[Kanstantsin Shautsou]

> --
> You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/tTJG_6eiWPg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0DfZGzHuRBo38qv_eG8cKabWWC84aN_VfN8wnK60og-A%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
I see difference traces when dealing with cloud. I.e. ServletException class not found for some magic getShel call. Sometimes i think async monitors causing traces because slave closed and deleted and some async work is in progress. Maybe Stephen C. knows where is architecture issue in all this async/sync work.