ICode9

精准搜索请尝试: 精确搜索
首页 > 其他分享> 文章详细

Tomcat报错 Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.

2019-02-28 18:02:21  阅读:339  来源: 互联网

标签:util errors java will 报错 coyote apache org ThreadPoolExecutor


 

 

 

信息: Error parsing HTTP request header
 Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
    at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:406)
    at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:380)
    at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
    at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:796)
    at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1372)
    at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
    at java.lang.Thread.run(Thread.java:745)
二月 28, 2019 5:53:05 下午 org.apache.coyote.http11.Http11Processor service
信息: Error parsing HTTP request header
 Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
    at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:406)
    at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:380)
    at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
    at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:796)
    at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1372)
    at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
    at java.lang.Thread.run(Thread.java:745)
 

 

解决方法

https://blog.csdn.net/zx1323/article/details/77018404

 

 

 

启动tomcat时看到日志上有异常

further occurrences of HTTP header parsing errors will be logged at DEBUG level.
 

百度很多博文都指向了一篇解析的很详细的博文:http://blog.csdn.net/codetomylaw/article/details/43407443

 

没啥耐心看了,等于说maxHttpHeaderSize默认配置上没有的,但默认值是8*1024 ,那我就调成了10*1024试试,然后就OK了,以后有时间再研究吧

修改tomcat   service.xml配置文件中的

 


 
  1. <Connector port="8080" protocol="HTTP/1.1"

  2. connectionTimeout="20000"

  3. maxHttpHeaderSize ="10240"

  4. redirectPort="8443" />

标签:util,errors,java,will,报错,coyote,apache,org,ThreadPoolExecutor
来源: https://blog.csdn.net/qq_35921382/article/details/88039041

本站声明: 1. iCode9 技术分享网(下文简称本站)提供的所有内容,仅供技术学习、探讨和分享;
2. 关于本站的所有留言、评论、转载及引用,纯属内容发起人的个人观点,与本站观点和立场无关;
3. 关于本站的所有言论和文字,纯属内容发起人的个人观点,与本站观点和立场无关;
4. 本站文章均是网友提供,不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属;如您发现该文章侵犯了您的权益,可联系我们第一时间进行删除;
5. 本站为非盈利性的个人网站,所有内容不会用来进行牟利,也不会利用任何形式的广告来间接获益,纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。

专注分享技术,共同学习,共同进步。侵权联系[81616952@qq.com]

Copyright (C)ICode9.com, All Rights Reserved.

ICode9版权所有