PK85315: WSWS3047E due to SAXException when processing a SOAP request for A WEBSERVICE MIGRATED FROM V5.1 TO V6.1

Fixes are available

APAR status

Closed as program error.

Error description

A WebService client that was successfully able to invoke a
WebService deployed to WebSphere Application Server 5.1 is
receiving the following error when invoking the same webservice
after it has been migrated to WebSphere Application Server 6.1


[4/9/09 15:28:12:984 CEST] 00000073 WebServicesSe E
com.ibm.ws.webservices.engine.transport.http.WebServicesServlet
doPost
WSWS3227E:  Error: Exception:
                                 WebServicesFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalExcepti
on
 faultString: org.xml.sax.SAXException: WSWS3047E: Error: Cannot
deserialize element ABC of bean
test.xframe.bin.bfutil.WS_B022V2.
Child element ABC does not belong in namespace
http://test.xframe.bin.usi.it.
Most likely, a third party web services platform has sent an
incorrect
SOAP message. Message being parsed:
 faultActor: null
 faultDetail:

org.xml.sax.SAXException: WSWS3047E: Error: Cannot deserialize
element
ABC of bean test.xframe.bin.bfutil.WS_B022V2.
Child element ABC does not belong in namespace
http://test.xframe.bin.usi.it.
Most likely, a third party web services platform has sent an
incorrect
SOAP message. Message being parsed:
        at
com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServ
icesFault.java:298)
        at
com.ibm.ws.webservices.engine.SOAPPart._getSOAPEnvelope(SOAPPart
.java:1090)
        at
com.ibm.ws.webservices.engine.SOAPPart.getAsSOAPEnvelope(SOAPPar
t.java:628)
        at
com.ibm.ws.webservices.engine.SOAPPart.getEnvelope(SOAPPart.java
:656)
        at
com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandlerChain
.
handleRequest(JAXRPCHandlerChain.java:301)


The problem with the incoming SOAP request is that the
WebServices client is a 3rd party WebServices implementation and
is sending a message that does not match the wsdl contract. The
incoming SOAP request does not have the right namespace. The
wsdl file for the WebService has a name space of
http://bfutil.bin.xframe.usi.it but the incoming SOAP request
has a namespace of 'http://test.xframe.bin.usi.it'.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server            *
*                  administrators migrating JAX-RPC            *
*                  applications from v5.1.                     *
****************************************************************
* PROBLEM DESCRIPTION: A SAXException occurs when you          *
*                      migrate a JAX-RPC web service from v5.1 *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR on   *
*                  the node receiving the web service message. *
****************************************************************
Suppose a JAX-RPC web service receives the following message:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" >
<soapenv:Body>
<getData xmlns='http://sample'>
<myData>
<myChildData>06170</myChildDaat>
</myData>
</getData>
</soapenv:Body>
</soapenv:Envelope>

The message will be correctly accepted if the wsdl file for
the web service indicates that namespace for myChildData is
{http://sample}.  The message will be correctly rejected if
the wsdl file indicates that the namespace for myChildData is
something other than {http://sample}.

The WebSphere Application Server v5.1 runtime does not contain
this validation check.

If you have an application installed on the V5.1 WebSphere
Application Server and the web service client is provided by
another (non-IBM) vendor, the other vendor may send an invalid
message.  Since v5.1 does not contain the validation check,
the application may succeed.

However if you migrate the application to v6.1, the
application will now fail due to the strict validation check.

The customer is asking for a mechanism to tolerate the
incorrect inbound message.

Problem conclusion

A new custom JVM/application property is introduced,
com.ibm.ws.webservices.jaxrpc.parse.tolerate.invalid.namespace.

When this property is set to "true", the JAX-RPC runtime will
attempt to tolerate the incorrect namespace on the inbound
message and use only the localPart of the element to determine
how to unmarshal the data.

If you enable debug trace for the following two modules:

com.ibm.ws.webservices.engine.encoding.ser.BeanDeserializer=all:
com.ibm.ws.webservices.engine.xmlsoap.builders.RequestResponsePr
ocessor=all

extra debug trace is generated in the trace.log when the
toleration occurs.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.27 and 7.0.0.7.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK85315
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-24
Closed date
2009-06-30
Last modified date
2009-10-05

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK85315: WSWS3047E due to SAXException when processing a SOAP request for A WEBSERVICE MIGRATED FROM V5.1 TO V6.1

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?