IBM Support

PI97582: WASPOSTUPGRADE FAILING WITH NULLPOINTEREXCEPTION COMING FROM THE SERVERINDEXCONFIG.

Fixes are available

9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Running WASpostUpgrade on dmgr profile fails with
    NullPointerException coming from the ServerIndexConfig, causing
    WASpostupgrade failing with below exception :
    
    
    [4/26/18 10:29:24:775 EDT] 00000001 WCCMDocumentR >  invoke
    Entry
        public abstract java.lang.String
     com.ibm.websphere.models.config.serverindex.
     ServerIndex.getHostName()
        com.ibm.websphere.models.config.serverindex.impl.
     ServerIndexImpl@1c5f2874
        [Ljava.lang.Object;@7365bd6f
        true
        interface com.ibm.websphere.models.config.serverindex
     .ServerIndex
     .
    [4/26/18 10:29:24:775 EDT] 00000001 XMLReflection >
    handleInvocationTargetException Entry
                                     java.lang.reflect.
             InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0
     (Native Method)
     .
    Caused by: java.lang.NullPointerException
     at com.ibm.ws.migration.postupgrade.common.
     ServerIndexConfig.setHostName(ServerIndexConfig.java:812)
     at sun.reflect.NativeMethodAccessorImpl.
     invoke0(Native Method)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Configuration Migration Tools        *
    ****************************************************************
    * PROBLEM DESCRIPTION: NullPointerException fails              *
    *                      WASPostUpgrade in ServerIndexConfig     *
    *                      or InetAddressManager                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem is caused by an InetAddress object being null
    after the call to resolve a hostname string, because the
    hostname is not resolvable from the machine running
    WASPostUpgrade. Migration does not check for the null case, so
    a NullPointerException occurs.
    This problem occurs in different locations in the code
    depending on version. In 8.5.5, it will occur in
    ServerIndexConfig in setHostName(). In 9.0, it will occur in
    InetAddressManager in getInstance().
    This can occur if the user is performing a remote migration
    and the target profile is on a system that is isolated from
    the source system it was on. It can also occur on 9.0 during
    local migrations if there are old hosts in the virtualhosts.xml
    file that cannot be resolved.
    

Problem conclusion

  • WASPostUpgrade was adjusted to handle the cases where
    InetAddresses are not found and not fail the migration.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.14 and 9.0.0.8.  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

    PI97582

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-05-03

  • Closed date

    2018-06-08

  • Last modified date

    2018-06-08

  • 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

  • R900 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:
04 May 2022