timja / jenkins-gh-issues-poc-06-18

0 stars 0 forks source link

[JENKINS-42834] Sporadical log warnings "badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp..." #3936

Open timja opened 7 years ago

timja commented 7 years ago

Logs like this are appearing since upgrading to Jenkins v 2.50 (and also updating a few Jenkins Plugins):

******:/var/log/jenkins$ grep "badMessage" *
jenkins.log:2017-03-14 10:28:01 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@4b64f1dd{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 10:36:05 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@24bff35f{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 11:05:21 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@df42f50{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 11:06:55 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@1a14713f{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 11:08:52 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@81dfefb{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 11:11:08 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@124bb288{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 11:11:45 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@7db69510{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 11:11:50 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@10f69010{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 12:16:59 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@205aa4cf{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 14:46:36 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@6abce810{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 14:47:04 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@1d079aba{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-15 10:06:11 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@24636165{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-15 10:14:52 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@58a457aa{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-15 10:15:44 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@4657ffe6{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-15 10:16:48 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@7f2b7ba6{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-15 15:40:13 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@300217e9{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-15 15:42:13 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@183cc81a{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-16 13:41:07 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@7cfd9ca{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-16 13:47:19 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn]   badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@602dc808{r=1,c=false,a=IDLE,uri=}

First log warning: 2017-03-14 10:28:01 (Jenkins release was on Saturday, 11 March)

And I updated Jenkins from v2.49 to v2.50 before (2017-03-14, ~9:10), and updated the following Jenkins Plugins (at about the same time):

Warning seems unrelated to execution of builds though, but rather related to some UI actions.

Sorry for the little details...


Originally reported by reinholdfuereder, imported from: Sporadical log warnings "badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp..."
  • status: Reopened
  • priority: Minor
  • resolution: Unresolved
  • imported: 2022/01/10
timja commented 7 years ago

sebglon:

same on jenkins 2.45

timja commented 7 years ago

reinholdfuereder:

Based on Sebastien's comment I re-checked in all the remaining old Jenkins logs and I am sorry for having to admit: these sporadical logs were really there before as well!

(Again I am not sure if that helps a lot...)

timja commented 7 years ago

vadamec:

I got this error on specific call, trying to save change in /configureSecurity and via Nginx as proxy with SSL termination. With direct access to Jenkins it's ok. So I guess some header/proxy_buffer size setup.

WARNING: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@34854272

{r=0,c=true,a=COMPLETED,uri=/configureSecurity/configure}

Version 2.55

timja commented 7 years ago

reinholdfuereder:

We are also using vadamec's setup of using Nginx as proxy with SSL termination.
As it has not re-occurred since then (2017-03-16) anymore, I dare to resolve this issue now. (However I am not sure about the resolution type: "Won't fix" or "Not a defect" might also be applicable?)

timja commented 7 years ago

jbochenski:

We are still getting this on Jenkins ver. 2.60.2 and quite often (20 warnings in 5 minutes sample)