IBM Support

PI18780: PORT TYPES REPORTED AS INVALID DURING WEB SERVICES APPLICATION DEPLOYMENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When deploying a Web Services application, the defaultmappings
    may not be found, resulting in a failed deployment.
    
    The server logs show error messages similar to the following:
    
    [5/14/14 16:53:04:229 CDT] 00000146 ClientBndUtil W
    WSWS0050E: The Web services client bind file,
    ibm-webservicesclient-bnd.xmi, contains port type
    {http://www.ibm.com/service/myservice/Notification/1.0}Notificat
    ionPortType which is not a valid port type for this client.
    
    This leads to a NullPointerException during deployment:
    
    [5/14/14 16:53:04:337 CDT] 00000146 SystemErr     R Caused by:
    java.lang.NullPointerException
    [5/14/14 16:53:04:337 CDT] 00000146 SystemErr     R  at
    com.ibm.ws.webservices.combined.deploy.ClientBindPreferredPortTa
    skHelper.validPreferredPort(ClientBindPreferredPortTaskHelper.ja
    va:859)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All JAX-WS WebService users of IBM          *
    *                  WebSphere Application Server                *
    ****************************************************************
    * PROBLEM DESCRIPTION: NullPointerException happened when      *
    *                      PreferredPortDescriptor could not be    *
    *                      found in cached PreferredPortMappings.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    To enhance performance, PreferredPortMappings was retrieved
    from cache directly and later some validation was done by it.
    However, for some reason, the cached data maybe corrupted, for
    example, a bad migration. Then the validation would fail and
    NPE possibly happened.
    

Problem conclusion

  • The behavior was improved. First the engine still would try to
    get data for validation from cache, if no related data was
    found, the engine would reconstruct PreferredPortMappings by
    the application metadata to continue validating.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.4.  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

    PI18780

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-27

  • Closed date

    2014-08-04

  • Last modified date

    2014-08-04

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 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":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022