tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 60592] New: org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
Date Mon, 16 Jan 2017 15:14:32 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=60592

            Bug ID: 60592
           Summary: org.apache.coyote.http11.Http11Processor.service Error
                    parsing HTTP request header
           Product: Tomcat 8
           Version: 8.5.6
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
          Assignee: dev@tomcat.apache.org
          Reporter: shenry@microautomation.com
  Target Milestone: ----

Created attachment 34631
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=34631&action=edit
Tomcat Zip with log files and Conf

Under this version of Tomcat we have noticed the
org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request
header error on two different servers, on two different days, that have the
same version of Tomcat.  The issue was resolved on one server by rebooting, but
the other server corrected itself.  When this error occurred on the servers it
caused the application running to result in the follow two errors until it
resolved itself a day later or it was corrected by the reboot.

org.apache.coyote.http11.Http11Processor.service Error processing request
org.apache.coyote.http11.Http11Processor.service Error finishing response

We had these servers running on Tomcat 8.0.33 64bit up until 12/15/2016, where
we did not see such errors occurring with the application.  

We are not aware of what caused this error so we cannot provide a test
scenario, but I have attached all of the logs that correspond to the server
that corrected itself a day after the issue started occurring.  

What we would like to know is, as I can see the issue was reported in the
Tomcat 9 beta, it appears it was never resolved.  Is there any resolution for
this error?  If we were to move to Tomcat 8.5.9 is there still a possibility it
could still occur?  Do you have any other details about what could be causing
this error to occur in your Tomcat version 8.5.6?

Please let me know if any additional logs would be helpful to investigate this
issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message