IBM Support

PH30608: NULLPOINTEREXCEPTION WHEN RUNNING WASPOSTUPGRADE FROM PROFILE ROOT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If bin/WASPostUpgrade.sh is invoked from a profile root
    directory, migration process fails with a
    NullPointerException.
    WAS90.MIGR
    
    [10/08/2020 14:12:45:031 CDT]
    java.lang.NullPointerException
    com.ibm.ws.migration.utility.Upgr
    adeException: java.lang.NullPointerException
    	at com.ibm.ws.migr
    ation.postupgrade.Restore.<init>(Restore.java:274)
    
    Caused by:
    java.lang.NullPointerException
    	at com.ibm.ws.migration.common.D
    efaultOSInfo.readCmdLineFile(DefaultOSInfo.java:532)
    	at com.ibm
    .ws.migration.common.DefaultOSInfo.<init>(DefaultOSInfo.java:153
    )
    	at
    com.ibm.ws.migration.common.LinuxInfo.<init>(LinuxInfo.java:47)
    

Local fix

  • Use WASPostUpgrade.sh(.bat) from WAS_INSTALL_ROOT/bin instead
    of PROFILE_ROOT/bin
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Version to Version Migration Tools   *
    ****************************************************************
    * PROBLEM DESCRIPTION: NullPointerException during             *
    *                      WASPostUpgrade, readCmdLineFile in      *
    *                      stack trace                             *
    ****************************************************************
    * RECOMMENDATION:  If possible, run WASPostUpgrade from the    *
    *                  WAS_HOME/bin directory.                     *
    ****************************************************************
    Problem is occurring because WASPostUpgrade is being run with
    a current working directory that includes the relative file
    path properties/version/profile.version, usually the profile's
    root directory. Due to the way WASPostUpgrade constructs a
    file path related to gathering OS info, this file may exist
    when WASPostUpgrade does not expect it to, causing it to pass
    a null user root to code that reads setupCmdLine.sh, which
    causes the error.
    

Problem conclusion

  • Migration was adjusted to properly check for null files before
    attempting to read the setupCmdLine script. WASPostUpgrade
    should now succeed regardless of the existence of
    properties/version/profile.version in the current working
    directory.
    
    The fix for this APAR is targeted for inclusion in fix pack
    9.0.5.7. For more information, see 'Recommended Updates for
    WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH30608

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-15

  • Closed date

    2020-10-19

  • Last modified date

    2020-10-19

  • 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

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900"}]

Document Information

Modified date:
20 October 2020