HI Stefan, Am Do., 13. Sep. 2018 um 18:16 Uhr schrieb Stefan Seifert < [email protected]>:
> hello jörg. > > we had a short discussion about this on our sling hackathon today: > > 1. check the configured response buffer size of the jetty engine that is > currently configured for your instance. if the response you expected is > smaller than the buffer size (in recent version this is 24KB i think), > error handling should work fine. > I don't want to change that buffer size, because it's hard to estimate what the maximum size of the rendered content is (and will be). Just setting to 100k and hope for the best is not what I would like to do. Also because it's very hard to monitor if your response exceeds that size. > > 2. if your response is smaller than this and it is still happening it is > possible that here are calls to response.flush() that should not be done. > the recent sling modules should be correct and not using response.flush() > during rendering, but check your environment if this is the case there as > well > > 3. additionally make sure the JSP files of your application or that are > used from the platform do not contain calls to response.flush()! > > Yes, that's something we can validate and figure out, but I've seen this in too many cases, and not always a flush() was repsonsible. Also it's some very hard to validate all scripts and occassions (especially if they are part of the framework you use). Jörg -- Cheers, Jörg Hoh, http://cqdump.wordpress.com Twitter: @joerghoh
