tomcat8 at 100% cpu when trying https on port 80(在端口 80 上尝试 https 时,tomcat8 处于 100% cpu)
问题描述
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.
in catalina.out
On firefox I get
SSL_ERROR_RX_RECORD_TOO_LONG
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
This is a tomcat bug: https://bz.apache.org/bugzilla/show_bug.cgi?id=57544
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的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:在端口 80 上尝试 https 时,tomcat8 处于 100% cpu


基础教程推荐
- REST Web 服务返回 415 - 不支持的媒体类型 2022-01-01
- 无法复制:“比较方法违反了它的一般约定!" 2022-01-01
- 修改 void 函数的输入参数,然后读取 2022-01-01
- Struts2 URL 无法访问 2022-01-01
- 问题http://apache.org/xml/features/xinclude测试日志4j 2 2022-01-01
- 使用堆栈算法进行括号/括号匹配 2022-01-01
- 存储 20 位数字的数据类型 2022-01-01
- 如何对 Java Hashmap 中的值求和 2022-01-01
- RabbitMQ:消息保持“未确认"; 2022-01-01
- Spring AOP错误无法懒惰地为此建议构建thisJoinPoin 2022-09-13