IBM Support

PH33596: THE WEBSPHERE WINDOWS SERVICE SHOULD NOT USE STARTSERVER.LOG FOR ITS LOGFILE.

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

  • The WebSphere Application server file startserver.log will show
    exceptions indicating the file is in use when the WebSphere
    service is defined to use startserver.log as the service
    logfile.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Windows    *
    *                  services users                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Logging is incorrect when the           *
    *                      WebSphere Windows service is            *
    *                      configured to use startServer.log.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WebSphere Application server writes data to the
    startServer.log file. Some products have documented adding the
    WebSphere Windows service (wasservice) using startServer.log
    as the service log. If the service is configured to use the
    same logfile as the application server, log entries will be
    overwritten and an exception stating that the file is in use
    may be reported.
    

Problem conclusion

  • The service has been modified to use startserver_service.log
    as its logfile when it is defined with logfile
    startserver.log.
    
    Requests have been submitted to update IBM documentation
    using startServer.log as the service logfile.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.20 and 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

    PH33596

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-01-20

  • Closed date

    2021-01-25

  • Last modified date

    2021-01-25

  • 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

  • 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:
02 November 2021