在端口80上尝试https时tomcat8在100％cpu上 [英] tomcat8 at 100% cpu when trying https on port 80

问题描述

当尝试使用 https：// localhost：8080 / 时，tomcat卡在100％带有 ip的cpu--[12 / Jan / 2017：12：14：23 +0100]在access_log和

When trying to connect to tomcat 8 using https://localhost:8080/ tomcat get stuck at 100% cpu with ip - - [12/Jan/2017:12:14:23 +0100] "-" 400 - - in the access_log and

Jan 12, 2017 1:23:50 PM org.apache.coyote.http11.AbstractHttp11Processor process
INFO: Error parsing HTTP request header
 Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.

在catalina.out

in catalina.out

在firefox上我得到

On firefox I get

SSL_ERROR_RX_RECORD_TOO_LONG

我尝试使用默认配置（在debian 8上全新安装）的tomcat8，并且发生了相同的事情。我知道我不应该在端口8080或80上尝试https，但是我在服务器上收到了这些请求，因此我必须重新启动tomcat才能修复100％的CPU使用率

I tried with tomcat8 with the default configuration (fresh install on debian 8) and the same thing is happening. I know I shouldn't try https on port 8080 or 80 but I get those requests on my server and I have to restart tomcat to fix the 100% cpu utilization

推荐答案

这是一个tomcat错误： https：/ /bz.apache.org/bugzilla/show_bug.cgi?id=57544

This is a tomcat bug: https://bz.apache.org/bugzilla/show_bug.cgi?id=57544

此问题已在树干中修复（9.0 .x开发），8.0.x以及8.0.19
及以上的7.0.x以及7.0.60起。

This has been fixed in trunk (9.0.x development), 8.0.x for 8.0.19 onwards and 7.0.x for 7.0.60 onwards.

这篇关于在端口80上尝试https时tomcat8在100％cpu上的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！