Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-19513

Jenkins should reconnect to a node after ChannelClosedException

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • core, remoting
    • The slave node is using Webstart to connect to the master.

      I tried running a job in Jenkins and got the following exception:

      [EnvInject] - Loading node environment variables.
      [EnvInject] - [ERROR] - SEVERE ERROR occurs: hudson.remoting.ChannelClosedException: channel is already closed
      FATAL: null
      java.lang.NullPointerException
      	at hudson.tasks.MailSender.createFailureMail(MailSender.java:279)
      	at hudson.tasks.MailSender.getMail(MailSender.java:154)
      	at hudson.tasks.MailSender.execute(MailSender.java:100)
      	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.cleanUp(MavenModuleSetBuild.java:1025)
      	at hudson.model.Run.execute(Run.java:1648)
      	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:506)
      	at hudson.model.ResourceController.execute(ResourceController.java:88)
      	at hudson.model.Executor.run(Executor.java:247)
      

      Hitting "build now" multiple times results in the same exception over and over again. I am expecting Jenkins to automatically reconnect with the node after this exception occurs but it does not.

      It looks like EnvInject plugin runs into this exception and passes the failure on to Jenkins which then runs into a NPE. Ideally this bug should be solved so that regardless how the plugins behave, Jenkins will be smart enough to reconnect (i.e. faulty plugins shouldn't block a reconnect).

            Unassigned Unassigned
            cowwoc cowwoc
            Votes:
            29 Vote for this issue
            Watchers:
            28 Start watching this issue

              Created:
              Updated: