IBM Support

PM81653: AFTER WASSERVICE DETECTS THAT THE SERVICE HAS ALREADY STARTED IT SETS THE STATE INCORRECTLY TO SERVER_STOPPED

Fixes are available

8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The server is started and then it waits for a change in the
    process state:
    Mon Nov 19 09:30:10 2012 1972 - WASServiceMain: Successful start
    of WAS process
    Mon Nov 19 09:30:10 2012 1972 - WASServiceMain: Waiting for
    multiple events
    
    wasservice is notified that the process terminated and enters
    the restart code :
    Mon Nov 19 09:45:19 2012 1972 - WASServiceMain: Waiting for
    multiple events finished : 0
    Mon Nov 19 09:45:19 2012 1972 - WASServiceMain: TERM_COMP rc :
    31
    Mon Nov 19 09:45:19 2012 1972 - WASServiceMain: restart loop
    restart = 1
    rc = 31
    Mon Nov 19 09:45:19 2012 1972 - WASServiceMain: enter restart
    loop
    
    5 seconds later, wasservice detects that the server has already
    been restarted :
    Mon Nov 19 09:45:24 2012 1972 - isServerRuningAlready:
    Mon Nov 19 09:45:24 2012 1972 - getRegistryValue:
    SYSTEM\CurrentControlSet\Services\IBMWAS70Service -
    Curam_01\Parameters\
    Mon Nov 19 09:45:24 2012 1972 - getRegistryValue:
    SYSTEM\CurrentControlSet\Services\IBMWAS70Service -
    Curam_01\Parameters\
    Mon Nov 19 09:45:24 2012 1972 - waitForPidFile: Waiting for pid
    file:
    D:\Logs\WAS\AppSrv01\Curam_01\Curam_01.pid
    Mon Nov 19 09:45:24 2012 1972 - waitForPidFile: trying to open
    pid file
    Mon Nov 19 09:45:24 2012 1972 - waitForPidFile: pid found
    breaking
    Mon Nov 19 09:45:24 2012 1972 - waitForPidFile: close pid file
    Mon Nov 19 09:45:24 2012 1972 - waitForPidFile: Got pid from
    file: 5220
    Mon Nov 19 09:45:24 2012 1972 -  serverProcess already running,
    pid =
    5220
    Mon Nov 19 09:45:24 2012 1972 - WASServiceMain: exit restart
    loop
    Mon Nov 19 09:45:24 2012 1972 - WASServiceMain: Thread -1
    

Local fix

  • No workaround available
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users      *
    *                  using Microsoft Windows Services            *
    ****************************************************************
    * PROBLEM DESCRIPTION: If you use Microsoft Windows Services   *
    *                      to start the application server you     *
    *                      may see an incorrect status             *
    *                      displayed.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This problem only occurs if you have wasservice defined to
    automatically restart the application server and something
    else has restarted the application server before wasservice.
    

Problem conclusion

  • Code has been corrected to report the "started" status when
    wasservice detects that the application server is already
    started.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.29, 8.0.0.6 and 8.5.5.0. Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM81653

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-01-29

  • Closed date

    2013-02-01

  • Last modified date

    2016-11-15

  • 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

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM81653

Modified date: 15 November 2016