PM24498: WASSERVICE TIMED OUT GETTING PID FROM FILE, SERVICE STATUS IS STOPPED.

Fixes are available

APAR status

Closed as program error.

Error description

For WebSphere Application Server 6.1 on Microsoft Windows
Operating System.

From WasServiceTrace.log, we have the following:
startServer: Breaking out of wait for startServer.bat
getRegistryValue:
SYSTEM\CurrentControlSet\Services\IBMWAS61Service -

WASServiceMain: startServer returned.

getPidForServer: Checking [built] pid path for pid file:
waitForPidFile: trying to open pid file

parsePidFromStdout: not pid ADMU0116I:

waitForPidFile: Timed out getting pid from file.

Pid file is created and listed in startServer.log.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V6.1 and   *
*                  V7.0 users using Microsoft Windows services
****************************************************************
* PROBLEM DESCRIPTION: The application server may not be       *
*                      detected as started successfully        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When using Microsoft Windows services to start or stop the
WebSphere Application Server, the service may falsely report a
failure when there was a successful start.

Problem conclusion

The service code expected the application server to write a
file within 15 seconds of starting. In a busy environment
(such as startup), this file might not be produced within this
time frame. The time value was increased to 300 seconds to
allow for sufficient time for this file to be created.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.37 and 7.0.0.15.  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
PM24498
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-10-13
Closed date
2010-10-22
Last modified date
2011-02-11

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

R61W PSY
UP
R700 PSY
UP

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

Document Information

Modified date:
25 October 2021

Tips

PM24498: WASSERVICE TIMED OUT GETTING PID FROM FILE, SERVICE STATUS IS 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

R61W PSY

R700 PSY

Document Information

Share your feedback

Need support?