PK82849: MORE THAN ONE PIDWAITER THREAD FOR THE SAME APPSERVER PROCESS

Fixes are available

APAR status

Closed as program error.

Error description

There is a problem that can sometimes cause discovery to happen
more often that designed. Multiple PidWaiters get started for
the same server. PidWaiter may be hung after this and restart
the application server.

The following will appear in SystemOut log:

2/8/09 23:06:15:520 EDT] 000004f0 PidWaiter    A   ADML0064I:
Restarting an unreachable server "WebBroker_32c".

2/8/09 23:07:58:012 EDT] 00000437 PidWaiter    A   ADML0064I:
Restarting an unreachable server "WebBroker_32c".

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Versions 6.0.2, 6.1 and 7.0.         *
****************************************************************
* PROBLEM DESCRIPTION: More than one PidWaiter thread exists   *
*                      for one application server at the same  *
*                      time.                                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Nodeagent maintains the list of child processes (application
servers running under nodeagent) along with a RoutingTable.
During application server stop, node agent removes the
application server child entry from the RoutingTable. If the
child entry is disabled before removal, it may not be removed
from the routing table even though nodeagent tried to remove
it. So it is possible that when the process gets restarted,
PidWaiter and RoutingTable think that child is disabled. This
can cause the routing to the application server to be disabled
or there may be two PidWaiter threads after restart.

Problem conclusion

Code has been modified to properly handle the disabledChild so
only one Pidwaiter gets associated with it.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.37, 6.1.0.27 and 7.0.0.5.  Please refer to the
Recommended Updatespage for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK82849
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-18
Closed date
2009-04-16
Last modified date
2009-04-16

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

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
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":"BU059","label":"IBM Software w\/o TPS"},"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:
29 December 2021

Tips

PK82849: MORE THAN ONE PIDWAITER THREAD FOR THE SAME APPSERVER PROCESS

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?