PK74042: Scripted BPS commands wait for Alarm to pull notifications before starting next command

Fixes are available

APAR status

Closed as program error.

Error description

When a client pulls notification from the server using a
protocol other than RMI, there may be up to a 20 second wait
before a notification is received.  If a command takes less
than that, it will still wait the 20 seconds and will never
decrease the wait time unless more than one notification is
received.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
****************************************************************
* PROBLEM DESCRIPTION: When using wsadmin scripts, it may      *
*                      wait up to 20 seconds per command       *
*                      even if the command takes less time.    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When there were no notifications received during a wait
interval, the wait interval would increase up to 20 seconds.
The interval would never decrease until more than 1
notification was received.  In the case of BPS commands, there
would be only one notification and the script would wait for
its return.  This added a significant amount of time to the
duration of the script when the maximum wait time was reached.

Problem conclusion

The problem was fixed by changing the algorithm for
determining when to increase the wait time.  In addition to
waiting for multiple intervals before increasing the wait
time, it will now reset the wait time to the initial value of
3 seconds when a notification is received after the total wait
between notifications has been >= the max of 20 seconds.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.1.  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
PK74042
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-17
Closed date
2008-11-12
Last modified date
2008-11-12

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 October 2021

Tips

PK74042: Scripted BPS commands wait for Alarm to pull notifications before starting next command

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

Document Information

Share your feedback

Need support?