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

java.io.EOFException continue occur when using health check with aws network load balancer

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • core
    • Jenkins ver. 2.90

      Hi, we currently using AWS Network Load Balancer (http://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html) for jenkins jnlp service port auto discovery.

      But we continues got this exceptions.

      Nov 20, 2017 10:55:50 AM FINE hudson.TcpSlaveAgentListener
      Accepted connection #41,949 from /10.240.0.4:24748
      Nov 20, 2017 10:55:50 AM WARNING hudson.TcpSlaveAgentListener$ConnectionHandler run
      Connection #41949 failed java.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:197) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:241)
      

      slaves although are still working normally.

          [JENKINS-48106] java.io.EOFException continue occur when using health check with aws network load balancer

          Chris Lee created issue -
          Oleg Nenashev made changes -
          Labels Original: jnlp slave New: jnlp remoting slave
          Jeff Thompson made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          Aaron Trout made changes -
          Attachment New: nlb-hc.pcap [ 45240 ]
          Jeff Thompson made changes -
          Assignee New: Jeff Thompson [ jthompson ]
          Resolution Original: Cannot Reproduce [ 5 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]
          Jeff Thompson made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Reopened [ 4 ] New: Closed [ 6 ]

            jthompson Jeff Thompson
            protosschris Chris Lee
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: