PK81630: TIMING ISSUE WITH PIDWAITER THREAD MAY CREATE HANG AND MAKE PIDWAITER DETECT UNREACHABLE APP SERVERS LATER THAN EXPECTED.

Fixes are available

APAR status

Closed as program error.

Error description

If Nodeagent is heavily loaded and we don't wait for
PidWaiter's contact thread to start, we may get into problems
with restarting appserver too early. Also if we don't wait for
contact thread to return, we may receive incorrect appserver
status, as PidWaiter's contact might be in progress.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Versions 6.1 and 7.0.                *
****************************************************************
* PROBLEM DESCRIPTION: If Nodeagent is heavily loaded, we      *
*                      may get into problems with restarting   *
*                      application servers too early.          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If Nodeagent is heavily loaded, there may be some delay in
starting PidWaiter's contact thread and also there may be some
delay to return whether an application server contact is
successful. If we don't wait for PidWaiter's contact thread to
start or return, we may get into problems with restarting
application servers too early, because PidWaiter's contact
might be in progress at that point.

Problem conclusion

Source code has been modified to wait for PidWaiter's contact
thread to start and wait for contact thread to return.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.33, 6.1.0.25 and 7.0.0.5.  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
PK81630
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-02
Closed date
2009-04-07
Last modified date
2009-04-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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z 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

PK81630: TIMING ISSUE WITH PIDWAITER THREAD MAY CREATE HANG AND MAKE PIDWAITER DETECT UNREACHABLE APP SERVERS LATER THAN EXPECTED.

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?