monasca-api log flooded with jetty parser errors (java api)

[Bradley Klein]

Using the latest java code from 3/17/2016, seeing tons of this in the api log:

WARN [2016-03-18 14:42:01,980] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@6f19e5fb{r=1,a=IDLE,uri=-}
WARN [2016-03-18 14:42:01,980] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@6f19e5fb{r=1,a=IDLE,uri=-}
WARN [2016-03-18 14:42:01,980] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@6f19e5fb{r=1,a=IDLE,uri=-}
WARN [2016-03-18 14:42:01,980] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@6f19e5fb{r=1,a=IDLE,uri=-}

[Craig Bryant (craig-bryant)]

@brad Are you still seeing these error messages? We're not seeing them in any of our systems.

[Bradley Klein (brad-klein)]

Craig,

Thanks for following up. I think we've narrowed this to some mis-behaving custom metrics pushing code here at TWC, but I don't have the smoking gun yet. Should know more in a day or so...

Thanks!
Brad

[Olaf Heydorn (olaf-heydorn)]

I get the same error messages pushing a lot of our own kubernetes metrics to monasca-api.

WARN [2016-04-26 11:20:45,726] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@25d64a61{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:45,726] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@25d64a61{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:45,727] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@25d64a61{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:45,727] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@25d64a61{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:48,327] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@1f0984c3{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:48,327] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@1f0984c3{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:48,327] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@1f0984c3{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:48,327] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@1f0984c3{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:48,327] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@1f0984c3{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:48,327] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@1f0984c3{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:48,777] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@51db84e1{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:48,777] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@51db84e1{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:48,777] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@51db84e1{r=1,a=IDLE,uri=-}
WARN [2016-04-26 11:20:48,777] org.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@51db84e1{r=1,a=IDLE,uri=-}

[Ryan (ryan-brandt)]

Any further information on this bug? Has this been resolved?

[Bradley Klein (brad-klein)]

Ryan -- we've haven't seen in much lately, and when we do it's typically been a mis-behaving custom client. So I think we can close...