Hello Tomcat Users community, currently I have an application hosted in
Tomcat 8.5.23 that is getting connect resets when calling a web service.

Network traces show that duplicate headers in the web service request (see
below) and probable cause.  The application devs are not seeing where their
code is causing this behavior.

Questions:
-Are there any known Tomcat issues that could contribute to this behavior?
-Are there troubleshooting methods for Tomcat itself that can help debug
the issue?  We've increased logging levels and are not seeing any events
that are helping us diagnose root cause.

Thanks in advance,

Randy

=============================
Example Request from Network Trace
============================


POST /WebServiceEndpoint HTTP/1.1
Content-Type: text/xml;charset=utf-8
SOAPAction: ""
Authorization: Basic XXXXXXXXXXXXXXXX=
HTTP_X_FORWARDED_FOR: 10.200.X.X
serverId: server.domain.org
SR_API_KEY: XXXXXXXXXXXXXXXXXXX
POST /WebServiceEndpoing HTTP/1.1
Content-Type: text/xml;charset=utf-8
SOAPAction: ""
Authorization: Basic XXXXXXXXXXXXXXXX=
serverId: server.domain.org
SR_API_KEY: XXXXXXXXXXXXXXXXXXX
SR_CATEGORY
Cache-Control: no-cache
Pragma: no-cache
User-Agent: Java/1.8.0_151
Host: destination.server.domain.org
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 613

<?xml version="1.0"?>
<tns:Envelope xmlns:tns="http://schemas.xmlsoap.org/soap/envelope/";>
  <tns:Body>

        Soap payload...

  </tns:Body>
</tns:Envelope>

Reply via email to