Hello Naveen, Recently we have had a similar issue migrating a webapp from another application server to tomcat. We solved it specifying <request-character-encoding>UTF-8</request-character-encoding> in the web.xml descriptor.
You can read here [1] the long story :) Hope it helps, Luis [1] https://cwiki.apache.org/confluence/display/TOMCAT/Character+Encoding El mié., 10 jun. 2020 a las 11:08, Naveen Kumar (<[email protected]>) escribió: > Hi All, > > I have a webapp A which has few SOAP services and I consume those services > from webapp B. > I started getting below error since I upgraded the tomcat to 9.0.31 (from > 9.0.24): > com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync Couldn't create SOAP > message due to exception: XML reader error: > javax.xml.stream.XMLStreamException: java.io.EOFException: Unexpected EOF > > Then I wrote a filter at webapp A to intercept the request and I could see > that some junk characters are added in the SOAP request. > > If I upgrade tomcat to 9.0.35, the error disappears. > > Problematic request: > LoggingFilter.doFilter - The servlet request soap mapping body is:à 8Ï > S(http://schemas.xmlsoap.org/soap/envelope/ð??? Envelope??? Body8Ï ns13 > > Correct request: > The servlet request soap mapping body is:<?xml version='1.0' > encoding='UTF-8'?><S:Envelope xmlns:S > > Does anyone know what could be the possible reason for this? > > Thanks in advance. > - Naveen > -- "Ever tried. Ever failed. No matter. Try Again. Fail again. Fail better." - Samuel Beckett
