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

Fixes are available

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?