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

blank page after login, log says: java.lang.RuntimeException: Header>6144

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
    • Similar Issues:

      Description

      We are using the LDAP-Plugin. We see the Login screen. Right after logging in, we only see a blank page (0 byte response). Before three days, it still worked fine. No idea if the addition of a new job suddenly overfilled the response header generation.

      The /var/log/jenkins/jenkins.log shows:

      Mar 18, 2016 4:10:39 PM org.eclipse.jetty.util.log.JavaUtilLog warn
      WARNING: header full: java.lang.RuntimeException: Header>6144
      

      When I reload the blank page, another "Header>6144"-message appears in the log.
      The intervalled jobs still run in the background, but we are not able to see the GUI anymore.

      When we set <useSecurity>false</useSecurity> in the config.xml and restart, it works fine. So it must have sth. to do with the security header cookies or header refreshes (page reloads).

      Problem possibly related to:
      JENKINS-25046
      JENKINS-19946

        Attachments

          Issue Links

            Activity

            Hide
            mzahriya15 Mohammed Zahriya added a comment -

            I am getting the same error in my logs after configuring AD and Kerberos on my Instance of Jenkins running on Linux as well.

            Has anyone been able to figure this out?

            Jul 05, 2016 8:16:58 PM winstone.Logger logInternal
            INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled
            Jul 05, 2016 8:16:58 PM org.eclipse.jetty.util.log.JavaUtilLog warn
            WARNING: Header is too large >8192
            Jul 05, 2016 8:16:58 PM org.eclipse.jetty.util.log.JavaUtilLog warn
            WARNING: badMessage: 413 for HttpChannelOverHttp@2e27454b

            {r=0,c=false,a=IDLE,uri=/}

            Jul 05, 2016 8:16:58 PM org.eclipse.jetty.util.log.JavaUtilLog warn
            WARNING: Header is too large >8192
            Jul 05, 2016 8:16:58 PM org.eclipse.jetty.util.log.JavaUtilLog warn
            WARNING: badMessage: 413 for HttpChannelOverHttp@75eb7657

            {r=0,c=false,a=IDLE,uri=/favicon.ico}
            Show
            mzahriya15 Mohammed Zahriya added a comment - I am getting the same error in my logs after configuring AD and Kerberos on my Instance of Jenkins running on Linux as well. Has anyone been able to figure this out? Jul 05, 2016 8:16:58 PM winstone.Logger logInternal INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled Jul 05, 2016 8:16:58 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: Header is too large >8192 Jul 05, 2016 8:16:58 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: badMessage: 413 for HttpChannelOverHttp@2e27454b {r=0,c=false,a=IDLE,uri=/} Jul 05, 2016 8:16:58 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: Header is too large >8192 Jul 05, 2016 8:16:58 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: badMessage: 413 for HttpChannelOverHttp@75eb7657 {r=0,c=false,a=IDLE,uri=/favicon.ico}
            Hide
            danielbeck Daniel Beck added a comment -

            Do you send a giant cookie header to Jenkins?

            Show
            danielbeck Daniel Beck added a comment - Do you send a giant cookie header to Jenkins?
            Hide
            ssbarnea Sorin Sbarnea added a comment - - edited

            To be clear: this error is caused by Jenkins sending a too big header as part of the response, not the client. In fact the client is sending a header < 500 bites. We observed this behaviour on an instance with LDAP login enabled and especially on the /console page. It did not happen while requesting the /textConsole page.

            My impression is that http://stackoverflow.com/questions/20083651/jersey-client-post-results-in-header-full-java-lang-runtimeexception-header could be used to increase the limit of the header size.

            Show
            ssbarnea Sorin Sbarnea added a comment - - edited To be clear: this error is caused by Jenkins sending a too big header as part of the response, not the client. In fact the client is sending a header < 500 bites. We observed this behaviour on an instance with LDAP login enabled and especially on the /console page. It did not happen while requesting the /textConsole page. My impression is that http://stackoverflow.com/questions/20083651/jersey-client-post-results-in-header-full-java-lang-runtimeexception-header could be used to increase the limit of the header size.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            In order to set proper expectation, I have unassigned Kohsuke from this tickets.
            Currently there is no Default assignee in the LDAP plugin, any contributions will be appreciated.

            Show
            oleg_nenashev Oleg Nenashev added a comment - In order to set proper expectation, I have unassigned Kohsuke from this tickets. Currently there is no Default assignee in the LDAP plugin, any contributions will be appreciated.

              People

              • Assignee:
                Unassigned
                Reporter:
                paulklumpp Paul Klumpp
              • Votes:
                2 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated: