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

ClosedChannelException in log (excessive)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: jira-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.3
      java version "1.8.0_40"
      Java(TM) SE Runtime Environment (build 1.8.0_40-b26)
      Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)
      CentOS release 6.6 (Final)
    • Similar Issues:

      Description

      I just update to version 2 (2.3) and I am getting this logged every second. Any idea on how I can find out what is triggering this?

      May 12, 2016 5:22:53 PM org.apache.http.impl.nio.client.LoggingAsyncRequestExecutor exception
      SEVERE: http-outgoing-1 [CLOSED] HTTP protocol exception: null
      java.nio.channels.ClosedChannelException
              at sun.nio.ch.SocketChannelImpl.ensureReadOpen(SocketChannelImpl.java:257)
              at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:300)
              at org.apache.http.nio.reactor.ssl.SSLIOSession.receiveEncryptedData(SSLIOSession.java:346)
              at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:377)
              at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:118)
              at org.apache.http.impl.nio.reactor.BaseIOReactor.validate(BaseIOReactor.java:220)
              at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:284)
              at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
              at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:613)
              at java.lang.Thread.run(Thread.java:745)
      
      May 12, 2016 5:22:54 PM org.apache.http.impl.nio.client.LoggingAsyncRequestExecutor exception
      SEVERE: http-outgoing-1 [CLOSED] HTTP protocol exception: null
      java.nio.channels.ClosedChannelException
              at sun.nio.ch.SocketChannelImpl.ensureReadOpen(SocketChannelImpl.java:257)
              at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:300)
              at org.apache.http.nio.reactor.ssl.SSLIOSession.receiveEncryptedData(SSLIOSession.java:346)
              at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:377)
              at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:118)
              at org.apache.http.impl.nio.reactor.BaseIOReactor.validate(BaseIOReactor.java:220)
              at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:284)
              at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
              at org.apache.http.impl.nio.reactor.AbstractMultiworkerIORe
      

        Attachments

          Issue Links

            Activity

            Hide
            aheritier Arnaud Héritier added a comment -

            I confirm that this issue seems to be essentially due to the jira plugin when your Jira server has either an invalid certificate (you need to fix it) or if you use a self-signed certificate (you need to install the certificate in the Master JVM)

            Show
            aheritier Arnaud Héritier added a comment - I confirm that this issue seems to be essentially due to the jira plugin when your Jira server has either an invalid certificate (you need to fix it) or if you use a self-signed certificate (you need to install the certificate in the Master JVM)
            Hide
            thirudhas Thirumurugan Dhasappan added a comment -

            Hi Team,

            We are executing CI execution using Jenkins with ver. 2.46, but we are interrupted with ClosedChannelException*[java.nio.channels.ClosedChannelException.* Kindly help us with any solution for this issue.

            With the above issue we are facing Caused: java.io.IOException: Backing channel 'JNLP4-connect connection from ***.*..*/*.*..*:**' is disconnected.  can anyone give a clear view about this issue and why it occurring. We hardly blocked with execution in Jenkins

            Show
            thirudhas Thirumurugan Dhasappan added a comment - Hi Team, We are executing CI execution using Jenkins with ver. 2.46, but we are interrupted with ClosedChannelException *[java.nio.channels.ClosedChannelException .* Kindly help us with any solution for this issue. With the above issue we are facing  Caused: java.io.IOException: Backing channel 'JNLP4-connect connection from ***. * . . * / * . * . . * : ** ' is disconnected.   can anyone give a clear view about this issue and why it occurring. We hardly blocked with execution in Jenkins
            Hide
            jz38676 Jason Zhou added a comment -

            We have been seeing this excessive log problem too:

            Ubuntu 16.04 (4.4.0-93-generic)

            openjdk 1.8.0_131

            Jenkins 2.46.1

            nginx 1.10.3

            JIRA Plugin 2.3

             

            Show
            jz38676 Jason Zhou added a comment - We have been seeing this excessive log problem too: Ubuntu 16.04 (4.4.0-93-generic) openjdk 1.8.0_131 Jenkins 2.46.1 nginx 1.10.3 JIRA Plugin 2.3  
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Thirumurugan Dhasappan whatever was your request, it should have been reported as a separate ticket

            According to Arnaud Héritier's above, I am removing Jenkins Core from equation. Note that JIRA plugin is generally unreliable on Jenkins instances due to JENKINS-48357.

            Show
            oleg_nenashev Oleg Nenashev added a comment - Thirumurugan Dhasappan whatever was your request, it should have been reported as a separate ticket According to Arnaud Héritier 's above, I am removing Jenkins Core from equation. Note that JIRA plugin is generally unreliable on Jenkins instances due to JENKINS-48357 .
            Hide
            warden Radek Antoniuk added a comment -

            This should be fixed in jira-plugin 2.5.2. If not, please reopen with current logs from current Jenkins and jira-plugin, thanks!

            Show
            warden Radek Antoniuk added a comment - This should be fixed in jira-plugin 2.5.2. If not, please reopen with current logs from current Jenkins and jira-plugin, thanks!

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              toga98 Russ Tennant
              Votes:
              8 Vote for this issue
              Watchers:
              16 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: