IBM Support

PH59374: LIBERTY SERVER FAILS TO START UNLESS FULLY QUALIFIED PATH TO SERVER SCRIPT IS USED.

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

  • `bin/server start` reports:
    
    Error: Unable to access jarfile
    ./../bin/tools/ws-server.jar
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Core on z/OS, IBMi, HP-UX    *
    *                  and AIX                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: The "server start" command fails on     *
    *                      some Linux distros.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    On some unix systems  when the "server start" command is
    issued  from the bin directory it fails with the following
    error message:
    Error: Unable to access jarfile ./../bin/tools/ws-server.jar
    A temporary solution to the problem is to specify the full
    path to the server script on the command line.  For example:
    /opt/wlp/bin/server start
    Note the path includes "..".   This was an unintentional
    change introduced in 23.0.0.12.   This changed the name of the
    process as it is displayed in the linux "ps" command.
    

Problem conclusion

  • The problem was a program error in setting the Liberty
    installation directory location in the "server" script.
    The problem was introduced in 23.0.0.12, and has been
    corrected and no longer includes ".." in the path.
    
    The fix for this APAR is targeted for inclusion in fix pack
    24.0.0.1 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

    PH59374

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-01-24

  • Closed date

    2024-02-28

  • Last modified date

    2024-03-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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
04 April 2024