PK85080: INTELLIGENT LOAD DISTRIBUTION FEATURE CURRENTLY REQUIRES A REBOOT OF SERVER TO RETREIVE ODC INFORMATION FOR STATIC INFO.

Fixes are available

APAR status

Closed as program error.

Error description

A future DataPower Release will have an Intelligent Load
Distribution feature.  This feature leverages the work that
has been done on WebSphere Application Server Network
Deployment edition and WebSphere Virtual Enterprise.  The
DataPower appliance periodically retrieves On Demand
Configuration (ODC) information containing cluster membership
and weight information.  This ODC information is available in
both the Network Deployment and Virtual Enterprise environment,
and is retrieved through a servlet that is able to query and
return this information. In the case of a Network Deployment
environment, weight information associated with a server is
statically configured. In the case of  WebSphere Virtual
Enterprise, weight information may be statically or
dynamically configured.

The problem is that in the static case, the weight information
is not updated until someone reboots the server whose weights
were changed. This presents a significant usability problem as
the customer expects to be able to modify the weights through
the deployment manager and then to see these weights show up
quickly and automatically on the Datapower device.  By forcing a
reboot, the server or servers will have a significant outage
whenever the weights must be changed.  This is an insignificant
problem if there are only a few servers, but it is quite a
hassle when several servers are involved.

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0                        *
****************************************************************
* PROBLEM DESCRIPTION: When cluster member runtime weights     *
*                      are updated, the value is not           *
*                      reflected in the On Demand              *
*                      Configuration tree.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Changes to the runtime weights are not monitored by the On
Demand Configuration (ODC) tree, making it impossible to update
weight values in the ODC tree without restarting the server in
question.

Problem conclusion

Logic had been added to cause ODC to listen for runtime server
weight changes and reflect the values into the ODC tree data.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.27 and 7.0.0.7. 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
PK85080
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-04-21
Closed date
2009-05-20
Last modified date
2009-05-20

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
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

PK85080: INTELLIGENT LOAD DISTRIBUTION FEATURE CURRENTLY REQUIRES A REBOOT OF SERVER TO RETREIVE ODC INFORMATION FOR STATIC INFO.

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

R700 PSY

Document Information

Share your feedback

Need support?