PK95311: JAX-WS Server is sending an incorrect VersionMismatch fault

Fixes are available

APAR status

Closed as program error.

Error description

When the JAX-WS server runtime receives a message that uses
the wrong SOAP version, it must respond with a soapenv:Fault
that indicates a VersionMismatch.

For example if a client sends a SOAP 1.1 message to a SOAP 1.2
JAX-WS endpoint, the JAX-WS server runtime should respond with
a message like this:

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Body>
        <soapenv:Fault>
            <faultcode>soapenv:VersionMismatch</faultcode>
            <faultstring>Transport level information does not
match with
SOAP Message namespace URI</faultstring>
            <detail></detail>
        </soapenv:Fault>
    </soapenv:Body>
</soapenv:Envelope>

However in some cases the server responds with a message like
this:

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Body>
        <soapenv:Fault>
            <faultcode>S:VersionMismatch</faultcode>
            <faultstring>Transport level information does not
match with
SOAP Message namespace URI</faultstring>
            <detail></detail>
        </soapenv:Fault>
    </soapenv:Body>
</soapenv:Envelope>

Note that the faultcode contains a undefined prefix (S)
instead of the defined prefix (soapenv).  The undefined prefix
may cause an unpredictable parsing or deserialization error on
the client that receives the inbound soapenv:Fault message.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
*                  of JAX-WS                                   *
****************************************************************
* PROBLEM DESCRIPTION: The JAX-WS runtime sends an incorrect   *
*                      VersionMismatch Fault message           *
****************************************************************
* RECOMMENDATION:  Install a fix pack that contains this APAR  *
*                  on the node that sends the invalid          *
*                  VersionMismatch                             *
****************************************************************
When the JAX-WS server runtime receives a message that uses
the wrong SOAP version, it must respond with a soapenv:Fault
that indicates a VersionMismatch.

For example if a client sends a SOAP 1.1 message to a SOAP 1.2
JAX-WS endpoint, the JAX-WS server runtime must respond with
a Fault message indicating that a version mismatch is
detected.  Here is an example of an appropriate message:

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Body>
        <soapenv:Fault>
            <faultcode>soapenv:VersionMismatch</faultcode>
            <faultstring>Transport level information does not
match with
SOAP Message namespace URI</faultstring>
            <detail></detail>
        </soapenv:Fault>
    </soapenv:Body>
</soapenv:Envelope>

However in some cases the server responds with a message like
this:

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Body>
        <soapenv:Fault>
            <faultcode>S:VersionMismatch</faultcode>
            <faultstring>Transport level information does not
match with
SOAP Message namespace URI</faultstring>
            <detail></detail>
        </soapenv:Fault>
    </soapenv:Body>
</soapenv:Envelope>

Note that the faultcode contains a undefined prefix (S)
instead of the defined prefix (soapenv).  The undefined prefix
may cause an unpredictable parsing or deserialization error on
the client that receives the inbound soapenv:Fault message.

Problem conclusion

The values of the Fault's faultcode element are defined by the
SOAP specification.  According to the specification, the
values are qualified names, and the qualified names must use
the namespace defined by SOAP.  A change was made to the
JAX-WS engine to ensure that the outbound Fault's faultcode
valueuses a prefix that is defined to the namespace specified
by the SOAP specification.

The fix for this APAR is currently targeted for inclusion in
fix pack 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
PK95311
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-02
Closed date
2009-10-01
Last modified date
2009-10-01

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

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK95311: JAX-WS Server is sending an incorrect VersionMismatch fault

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

R700 PSY

Document Information

Share your feedback

Need support?