IBM Support

PH30529: 'WAS SERVICE ENTERED THE RUNNING STATE.' MSG IS SOMETIMES RECORDED TWICE.

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

  • When using the WebSphere Windows service, the service control
    manager event (id 7036)stating 'WebSphere service
    entered the running state.' may be reported twice.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users      *
    *                  using Microsoft Windows services with       *
    *                  WebSphere                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Microsoft service control event 7036,   *
    *                      indicating a service is running, may    *
    *                      be reported twice for a WebSphere       *
    *                      service.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a service is started, Microsoft expects the service to
    enter the running state within two minute (by default). If a
    service does not report that it has entered the running state
    promptly, Windows displays a message that the service is not
    responding as expected.
    The default timeout can be changed with a registry setting but
    the two minutes is the maximum timeout as such WebSphere can
    not tune this setting to a more appropriate value for its
    service. To prevent false errors, the WebSphere service reports
    that the service has entered the running state before the two
    minute expiration occurs.
    

Problem conclusion

  • When WebSphere initialization completes, the service code
    reports entering the running state and the Windows service
    control manager reports event 7036. When WebSphere
    initialization time exceeded the service timeout period, the
    event would be reported twice.
    
    If monitoring the event log to determine when the WebSphere
    server is available, the application specific event 103 should
    be used. The server is available for use when WebSphere event
    103 is logged in the event log.
    
    WebSphere event 103 reports: "The <service_name> service was
    started."
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.19 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

    PH30529

  • 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

    2020-10-14

  • Closed date

    2020-12-07

  • Last modified date

    2020-12-07

  • 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

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
08 December 2020