On 16/12/2018 03:01, Kohei Nozaki wrote:
> Hello,
>
> It turned out that the "sjsxp" library which JAX-WS RI v2.1.3 uses makes
> Tomcat behave this way. I tried a different version of JAX-WS RI (v2.1.7)
> which doesn't use the "sjsxp" library anymore and it solved the issue.
Thanks for reportin
Hello,
It turned out that the "sjsxp" library which JAX-WS RI v2.1.3 uses makes Tomcat
behave this way. I tried a different version of JAX-WS RI (v2.1.7) which
doesn't use the "sjsxp" library anymore and it solved the issue.
A very similar issue posted on the Metro mailing list:
http://metro.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kohei,
On 12/1/18 10:06, Kohei Nozaki wrote:
> Hello Konstantin, thanks for sharing the valuable information.
>
>> On Dec 1, 2018, at 19:00, Konstantin Kolinko
>> wrote:
>>
>>> * Our downstream Nginx instance (The client of our Tomcat
>>> instanc
Hello Konstantin, thanks for sharing the valuable information.
> On Dec 1, 2018, at 19:00, Konstantin Kolinko wrote:
>
>> * Our downstream Nginx instance (The client of our Tomcat instance) recorded
>> the error "upstream sent no valid HTTP/1.0 header while reading response
>> header from upst
bly
> downgrades the connection to HTTP/0.9. Do you think it's possible? The
> comments can be seen from the URL below:
>
> https://stackoverflow.com/questions/53496598/tomcat-occasionally-returns-a-response-without-http-headers#comment93976313_53552752
1. See the official FAQ
error "upstream sent no valid HTTP/1.0 header while reading response header
from upstream" at that time and the error makes perfect sense concerning the
response which has neither HTTP status line nor HTTP headers.
Speaking of a possibility of a bug, a person commented on the Stackoverflow
questi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kohei,
On 11/29/18 20:19, Kohei Nozaki wrote:
> I'm investigating a problem where Tomcat (7.0.92) returns a
> response with no HTTP headers very occasionally. It happened during
> a load test.
>
>
> According to the captured packets by Wireshark,
Hello,
I'm investigating a problem where Tomcat (7.0.92) returns a response
with no HTTP headers very occasionally. It happened during a load test.
According to the captured packets by Wireshark, after Tomcat receives a
request it just returns only a response body. It returns neither a
sta
