본문 바로가기
IBM - old/WAS 문제&해결

WSWS3052E: Error: Bad envelope namespace

by freeman98 2016. 5. 9.

http://www-01.ibm.com/support/docview.wss?uid=swg21405935

WSWS3052E: Error: Bad envelope namespace

 Technote (troubleshooting)
 
Problem(Abstract)
The following invalid namespace exception could be thrown by WebSphere Application Server for an incoming SOAP message.

org.apache.commons.logging.impl.Jdk14Logger debug
interceptDeserializationException: WSWS3052E: Error: Bad envelope
namespace: http://schemas.xmlsoap.org/soap/envelope WSWS3052E: Error:
Bad envelope namespace: http://schemas.xmlsoap.org/soap/envelope
at
com.ibm.ws.webservices.engine.xmlsoap.builders.SOAPEnvelopeBuilder.start
Element(SOAPEnvelopeBuilder.java:163)
at
com.ibm.ws.webservices.engine.events.P2DConverter.flush(P2DConverter.jav
a:860)
at
com.ibm.ws.webservices.engine.events.P2DConverter.startElement(P2DConver
ter.java:314)
at
com.ibm.xml.xlxp.api.sax.impl.SAX2ParserBase.startElementAction(SAX2Pars
erBase.java:232)
at
com.ibm.xml.xlxp.api.was.WSXMLReader.startElementAction(WSXMLReader.java
:139)
at
com.ibm.xml.xlxp.api.sax.impl.SAX2ParserBase.startElementEvent(SAX2Parse
rBase.java:216)
at
com.ibm.xml.xlxp.api.was.WSXMLReader$WSScannerHelper.produceStartElement
Event(WSXMLReader.java:370)

Incoming SOAP message:

[9/20/09 18:16:18:412 GMT] 00000042 MessageTrace 3 WSWS3570I: Inbound
HTTP SOAP response:
Content-Type: text/xml; charset="utf-8"
Message contents:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soapenv:Body>
 

Resolving the problem
The proper namespace for SOAP 1.1 is
"http://schemas.xmlsoap.org/soap/envelope/"

Here is the message that the WebSphere Application Server Web Service Engine receives:
[9/20/09 18:16:18:412 GMT] 00000042 MessageTrace 3 WSWS3570I: Inbound
HTTP SOAP response:
Content-Type: text/xml; charset="utf-8"
Message contents:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soapenv:Body>

Note that the inbound message defines the namespace as:
"http://schemas.xmlsoap.org/soap/envelope"

Note that the incoming namespace does not have the final slash "/"; thus it is not a valid SOAP namespace.

The WebSphere Application Server is responding correctly to this invalid namespace. It needs to be determined why the node that sends this message is sending an incorrect namespace.

Note that this is only one of the reasons why the above mentioned exception could occur.


댓글