Re: 500: Response header too large
Thanks very much for the response. You are correct, clearing the cache solved that issue. -Alan On Monday, October 23, 2023 at 6:40:27 AM UTC-6 db...@cloudbees.com wrote: > On Fri, Oct 20, 2023 at 8:38 PM alan.l...@gmail.com > wrote: > >> Sorry to bump, but any ideas? I get the stacktrace hitting the logout >> link and a white page, but it never actually logs out. A back button press >> puts me back logged into Jenkins. >> > > The logout attempts to clear cookies as they can accumulate after many > restarts/updates, each time with a different ID. I guess it's possible that > your requests (with a huge Cookie header) are fine, but the response, > trying to clear them all out, is not. > Diagnose by checking what your Cookie request header is, I expect you send > dozens of session cookies. > Try login/logout from a private browsing window, if that works it's an > indicator your cookies are a problem. > If so, temporarily resolve this issue by clearing browsing data in your > browser (and use the logout more often). > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/15fb31e5-c908-433d-98fe-ca7c2b6ec198n%40googlegroups.com.
Re: 500: Response header too large
On Fri, Oct 20, 2023 at 8:38 PM alan.l...@gmail.com wrote: > Sorry to bump, but any ideas? I get the stacktrace hitting the logout > link and a white page, but it never actually logs out. A back button press > puts me back logged into Jenkins. > The logout attempts to clear cookies as they can accumulate after many restarts/updates, each time with a different ID. I guess it's possible that your requests (with a huge Cookie header) are fine, but the response, trying to clear them all out, is not. Diagnose by checking what your Cookie request header is, I expect you send dozens of session cookies. Try login/logout from a private browsing window, if that works it's an indicator your cookies are a problem. If so, temporarily resolve this issue by clearing browsing data in your browser (and use the logout more often). -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMo7PtLBMd1rpMT-jZOkf5xpcpcYeEZ%3DrP30pEXoXDVQOxB1Lg%40mail.gmail.com.
Re: 500: Response header too large
Sorry to bump, but any ideas? I get the stacktrace hitting the logout link and a white page, but it never actually logs out. A back button press puts me back logged into Jenkins. On Thursday, October 19, 2023 at 11:17:45 AM UTC-6 alan.l...@gmail.com wrote: > Meant to add the stack trace. See attached text file. > > On Thursday, October 19, 2023 at 10:53:54 AM UTC-6 alan.l...@gmail.com > wrote: > >> I'm trying to upgrade a Jenkins server from 2.401 to 2.414.3. All seems >> OK except I notice the "logout" link throws a blank page, and a stacktrace >> with the following: >> >> https://jenkins-test.xxx.xxx.com/logout >> org.eclipse.jetty.http.BadMessageException: 500: Response header too large >> >> I can find things about request header size, but changing that doesn't >> help. Can anyone suggest a place to look for the cause of this? What >> information is needed to debug it? >> >> This is the new Jenkins 2.414.3 LTS, running on >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, >> mixed mode, sharing) >> >> Thanks in advance. >> -Alan >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/da4910b1-b15e-4ad6-96ee-b8b9d16ead32n%40googlegroups.com.
Re: 500: Response header too large
Meant to add the stack trace. See attached text file. On Thursday, October 19, 2023 at 10:53:54 AM UTC-6 alan.l...@gmail.com wrote: > I'm trying to upgrade a Jenkins server from 2.401 to 2.414.3. All seems > OK except I notice the "logout" link throws a blank page, and a stacktrace > with the following: > > https://jenkins-test.xxx.xxx.com/logout > org.eclipse.jetty.http.BadMessageException: 500: Response header too large > > I can find things about request header size, but changing that doesn't > help. Can anyone suggest a place to look for the cause of this? What > information is needed to debug it? > > This is the new Jenkins 2.414.3 LTS, running on > OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, > mixed mode, sharing) > > Thanks in advance. > -Alan > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ea4cdb0c-b214-4f51-a3c3-93d4f48f0446n%40googlegroups.com. 2023-10-19 16:31:11.421+ [id=17]WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving https://jenkins-test.xxx.com/logout org.eclipse.jetty.http.BadMessageException: 500: Response header too large at org.eclipse.jetty.server.HttpConnection$SendCallback.process(HttpConnection.java:774) at org.eclipse.jetty.util.IteratingCallback.processing(IteratingCallback.java:243) at org.eclipse.jetty.util.IteratingCallback.iterate(IteratingCallback.java:224) at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:589) at org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:1046) at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:1123) at org.eclipse.jetty.server.HttpOutput.channelWrite(HttpOutput.java:270) at org.eclipse.jetty.server.HttpOutput.close(HttpOutput.java:623) at org.eclipse.jetty.server.Response.closeOutput(Response.java:980) at org.eclipse.jetty.server.Response.sendRedirect(Response.java:614) at org.eclipse.jetty.server.Response.sendRedirect(Response.java:545) at org.eclipse.jetty.server.Response.sendRedirect(Response.java:620) at javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:130) at javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:130) at org.springframework.security.web.util.OnCommittedResponseWrapper.sendRedirect(OnCommittedResponseWrapper.java:136) at javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:130) at javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:130) at org.kohsuke.stapler.ResponseImpl.sendRedirect(ResponseImpl.java:142) at org.kohsuke.stapler.ResponseImpl.sendRedirect2(ResponseImpl.java:158) at hudson.security.SecurityRealm.doLogout(SecurityRealm.java:334) at jenkins.model.Jenkins.doLogout(Jenkins.java:4371) at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:397) Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:401) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:409) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:207) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:140) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:558) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:59) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:900) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:698) at org.kohsuke.stapler.Stapler.service(Stapler.java:248) at javax.servlet.http.HttpServlet.service(HttpServlet.java:590) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764) at org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1665) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:163) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:114) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:160) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:160)
500: Response header too large
I'm trying to upgrade a Jenkins server from 2.401 to 2.414.3. All seems OK except I notice the "logout" link throws a blank page, and a stacktrace with the following: https://jenkins-test.xxx.xxx.com/logout org.eclipse.jetty.http.BadMessageException: 500: Response header too large I can find things about request header size, but changing that doesn't help. Can anyone suggest a place to look for the cause of this? What information is needed to debug it? This is the new Jenkins 2.414.3 LTS, running on OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing) Thanks in advance. -Alan -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/91f996ca-d957-499e-98b9-16dddaea20dcn%40googlegroups.com.
