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
- is related to
-
JENKINS-19946 NullPointerException when authentication fails using LDAP with Jenkins as a Jetty webapp
-
- Open
-
- links to
[JENKINS-33655] blank page after login, log says: java.lang.RuntimeException: Header>6144
Description |
Original:
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: {code} Mar 18, 2016 4:10:39 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: header full: java.lang.RuntimeException: Header>6144 {code} 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. |
New:
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: {code} Mar 18, 2016 4:10:39 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: header full: java.lang.RuntimeException: Header>6144 {code} 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. Problem possibly related to: JENKINS-25046 JENKINS-19946 |
Description |
Original:
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: {code} Mar 18, 2016 4:10:39 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: header full: java.lang.RuntimeException: Header>6144 {code} 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. Problem possibly related to: JENKINS-25046 JENKINS-19946 |
New:
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: {code} Mar 18, 2016 4:10:39 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: header full: java.lang.RuntimeException: Header>6144 {code} 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 |
Environment |
Original:
RHEL 7.2, Standalone Jenkins with Jetty (java -jar jenkins.war) 1.644 1.653 (currently latest) ldap-plugin Chrome, Firefox, InternetExplorer (browser does not seem to matter) Our Jenkins has no slaves. It's just the "master". It has about 146 jobs. |
New:
RHEL 7.2, Standalone Jenkins with Jetty (java -jar jenkins.war) 1.644 1.653 (currently latest) ldap-plugin 1.11 Chrome, Firefox, InternetExplorer (browser does not seem to matter) Our Jenkins has no slaves. It's just the "master". It has about 146 jobs. |
Workflow | Original: JNJira [ 169616 ] | New: JNJira + In-Review [ 183573 ] |
Remote Link | New: This issue links to "increase-jetty-header-size-limit (Web Link)" [ 15018 ] |
Link | New: This issue is related to JENKINS-19946 [ JENKINS-19946 ] |
Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] |