PM59129: WLM START CLUSTER MAY BE SLOW WHEN MANY APPLICATION SERVERS ARE INVOLVED

Fixes are available

APAR status

Closed as program error.

Error description

The start cluster goes out and queries the nodeagent, that query
is actually going out to every single application server on all
nodes involved.  This APAR will speed things up for large
environments, changing the wide query to the nodeagent that
actually goes out to all individual jvm's, so that this
queryNames call specifies 'process=nodeagent' which is a narrow
query and will only be used against the nodeagent to launch the
application servers.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  V7.0 and V8.0 clustering                    *
****************************************************************
* PROBLEM DESCRIPTION: Start cluster operation may be slow in  *
*                      environments with many nodes            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In environments with multiples nodes, it is possible that the
start cluster operation may be slow and/or result in thread
hands on the deployment manager or nodeagents during the start
process.  This can cause the overall start cluster operation to
time out.
The underlying problem is with some level of failed
communication between the nodeagent and the servers on it's
node while the cluster mbean is attempting to resolve the
location of all of the nodeagent mbeans to run the start
operation.

Problem conclusion

This APAR does not directly solve the underlying communication
issue that is happening between the nodeagents and their
cluster members, but changes the scope of the lookup being
done on the deployment manager such that this communication
between the nodeagents and cluster members should no longer
take place when the deployment manager is attempting to locate
all of the nodeagent mbeans.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.25 and 8.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
PM59129
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-27
Closed date
2012-03-14
Last modified date
2012-05-22

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

[{"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:
28 October 2021

Tips

PM59129: WLM START CLUSTER MAY BE SLOW WHEN MANY APPLICATION SERVERS ARE INVOLVED

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

Document Information

Share your feedback

Need support?