https://issues.apache.org/bugzilla/show_bug.cgi?id=54064
--- Comment #15 from dragos cernahoschi <dragos.cernahos...@gmail.com> --- I think I found a pattern for the slow connections. I've used in the last week only the java https connector, not the native connector. And the very slow connections(300s, 600s) still happen with the same rate: 0.01 - 0.02% off all requests. I checked the logs from the previous weeks when I was using the native connector and found they happen when a client with a dynamic IP have its IP changed mid time a request: it starts the request with an IP and waits the response on another one. It might happen on slow connections when receiving a larger response. So the only difference between the java connector and native connector is that the last one uses CPU intensively to solve this use case. After the request is served the CPU usage goes down. Why are the connectors slow in this case? What can it be done? If you have a patch for the native connector that solves at least the high CPU problem I'll try it. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
