IBM Support

PM31409: JAX-WS CLIENT MIGHT STOP WORKING WHEN A NEW OPERATION WAS ADDED TO THE JAX-WS PROVIDER

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When a new operation is added to a JAX-WS web service,
    and clients are not updated, the JAX-WS clients might stop
    working with an error message similar to this:
    
    Exception in thread "main" javax.xml.ws.WebServiceException:
    The Endpoint validation failed to validate due to the
    following errors:  :: Invalid Endpoint Interface ::  :: The
    operation names in the WSDL portType do not match the method
    names in the SEI or Web service implementation class.
    

Local fix

  • Re-generate the client with the local wsdl.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
    *                  V7.0 running JAX-WS proxy clients.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a remote service WSDL is updated     *
    *                      to add operations, existing clients     *
    *                      may fail WSDL validation.               *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack containing this APAR if  *
    *                  you need to add operations to JAX-WS        *
    *                  services without updating clients.          *
    ****************************************************************
    You might need to add operations to existing web services and
    update deployed clients at a later time.  Default client
    behavior is to validate the operations built into the client
    against the operations in WSDL and fail if they do not match.
    This might interfere with adding operations to existing web
    services.
    

Problem conclusion

  • JAX-WS client validation code is changed to examine a JVM
    property, jaxws.ignore.extraWSDLOps.  If there are more
    operations in  the WSDL than built into the client, and this
    property is set to true,  WSDL validation will succeed and the
    client can be invoked.
    
    For more details on how to set the JVM property,
    refer to the article "Java virtual machine custom properties"
    in the Information Center for your WebSphere Application
    Server version and operating system.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.19.In versions 8 and higher, this is fixed by
    PM70361, available in fixpacks 8.0.0.6 and 8.5.0.2.
    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

    PM31409

  • 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

    2011-01-27

  • Closed date

    2011-04-28

  • Last modified date

    2012-09-28

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM31409

Modified date: 28 September 2012