Describe the bug
When a SOAP request is received by our server, the response is always a HTTP 500 with the following message:
<?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode>S:Server</faultcode><faultstring>Undefined property javax.xml.ws.servlet.request</faultstring></S:Fault></S:Body></S:Envelope>
It only happens with the OpenTelemetry javaagent flag on. Otherwise we handle the request as expected.
Steps to reproduce
Just running the application with the javaagent connected reproduces the problem.
What did you expect to see?
A 200 OK HTTP response with some expected payload for success.
What did you see instead?
A 500 HTTP response with the response body as seen above.
What version are you using?
1.28.0 (also happened in 1.27.0)
Environment
Compiler: OpenJDK 11.0.9.1
OS: Debian 11
Runtime (if different from JDK above): OpenJDK Runtime Environment (build 11.0.14+9-post-Debian-1deb11u1)
OS (if different from OS compiled on): Debian 11
Additional context
It's not possible to provide a sample application, but I'm willing to try and debug/provide any additional context.
I decided to do some debugging on my own, and found something that I think might be helpful.
The problem seems to happen during a call to MetroServerSpanNaming#updateServerSpanName:
HttpServletRequest request = (HttpServletRequest) packet.get(MessageContext.SERVLET_REQUEST);
Could this be a configuration problem?
Describe the bug
When a SOAP request is received by our server, the response is always a HTTP 500 with the following message:
<?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode>S:Server</faultcode><faultstring>Undefined property javax.xml.ws.servlet.request</faultstring></S:Fault></S:Body></S:Envelope>It only happens with the OpenTelemetry javaagent flag on. Otherwise we handle the request as expected.
Steps to reproduce
Just running the application with the javaagent connected reproduces the problem.
What did you expect to see?
A 200 OK HTTP response with some expected payload for success.
What did you see instead?
A 500 HTTP response with the response body as seen above.
What version are you using?
1.28.0 (also happened in 1.27.0)
Environment
Compiler: OpenJDK 11.0.9.1
OS: Debian 11
Runtime (if different from JDK above): OpenJDK Runtime Environment (build 11.0.14+9-post-Debian-1deb11u1)
OS (if different from OS compiled on): Debian 11
Additional context
It's not possible to provide a sample application, but I'm willing to try and debug/provide any additional context.
I decided to do some debugging on my own, and found something that I think might be helpful.
The problem seems to happen during a call to
MetroServerSpanNaming#updateServerSpanName:Could this be a configuration problem?