IBM Support

PH47715: WEBSPHERE SERVICE CRASH IN NTDLL.DLL

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 Windows operating system may report a crash in NTDLL.DLL
    from the WebSphere module: wasservice.exe
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users      *
    *                  with Windows Services enabled               *
    ****************************************************************
    * PROBLEM DESCRIPTION: When WebSphere is defined as a Window   *
    *                      service, a crash may occur in           *
    *                      NTDLL.DLL from wasservice.exe           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the WebSphere service is started, a crash may occur in
    NTDLL.DLL. The crash is reported in the Windows Event Log. The
    service status indicates the service is not running after the
    crash occurs.
    

Problem conclusion

  • The service requires a unique log file. Some older
    documentation provided examples using the WebSphere
    startserver.log file as the service log file. It is not valid
    to use startserver.log as the service log file because that
    log file is used by other WebSphere processes. When the
    service detects that startserver.log is defined as the service
    log, it attempts to modify the log name. A crash occured
    during this process. The name modification was corrected to
    prevent the crash.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.23 and 9.0.5.13. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

  • Modify the service log file name to a name other than
    startserver.log to avoid this problem.
    

Comments

APAR Information

  • APAR number

    PH47715

  • 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

    2022-07-05

  • Closed date

    2022-07-19

  • Last modified date

    2022-09-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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

[{"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:
08 September 2022