https://bz.apache.org/bugzilla/show_bug.cgi?id=65402
--- Comment #49 from Stefan Eissing <ste...@eissing.org> --- I see 37 h2 worker busy at the time requests '66-289' to '66-295' arrive and that is the maximum in your sever configuration. The processing can only start when a worker becomes available again. You can mitigate that by an increased `H2MaxWorkers` configuration. The question is what usage your anticipate on that server when you take it live. Increasing numbers of users with these SSE request will eventually exhaust whatever worker limit you configure. Question: can you reduce the 30 seconds update time on the SSE generators? (The desired fix would be for apache to get rid of those workers directly when the client resets the stream, but that is not easily achieved.) -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
