Fixes are available
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
IIOP, MDB and internal work requests are showing inconsistent RMF QUEUED WAIT measurements. The queued wait time seems to fluctuate between a very low number and a much higher number. The higher number seems to include wait time spent on the WLM queue waiting to be picked up by a worker thread in a servant. The lower number omits the WLM Queue wait time.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V6.1.0 * **************************************************************** * PROBLEM DESCRIPTION: Inconsistent RMF workload activity * * report queue times are being reported * * for inbound requests. * **************************************************************** * RECOMMENDATION: * **************************************************************** A value used in the calculation of the queue time is the enclave execution start time. The enclave execution start time is defined by each enclave create using the EXSTARTDEFER parameter on the IWMECREA WLM Service when creating the WLM enclave. A value of "YES" for the EXSTARTDEFER parameter indicates that the enclave execution start time should begin when the first IWMSTBGN or IWMEJOIN is executed. A value of "NO" for the EXSTARTDEFER parameter indicates that the enclave execution start time should not begin when the first IWMSTBGN or IWMEJOIN is executed. The WebSphere for z/OS Application Server Control Region uses both values for the EXSTARTDEFER parameter depending on the request protocol and the contents of the request. This may cause inconsistent queue times in the RMF workload activity report.
Problem conclusion
The code has been modified to provide a consistent choice for the EXSTARTDEFER parameter value on the IWMECREA invocation. The value for the EXSTARTDEFER parameter will be supplied by a new environment variable "wlm_enclavecreate_exstartdefer". APAR PM24445 requires changes to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: http://www.ibm.com/software/webservers/appserv/library The following change to the WebSphere Application Server Version 6.1 Information Center will be made available in April, 2011. The following description of the wlm_enclavecreate_exstartdefer environment variable will be added to the "Application server custom properties that are unique for the z/OS platform" topic: wlm_enclavecreate_exstartdefer Specifies the value that you want used for the Workload Management Service EXSTARTDEFER parameter when you use the IWMECREA Workload Management Service to create an Enclave. The supported values are YES and NO. - Specifying YES indicates that the Enclave execution start time should begin when the first IWMSTBGN or IWMEJOIN is executed. - Specifying NO indicates that the Enclave execution start time should not begin when the first IWMSTBGN or IWMEJOIN is executed. See the z/OS Information Center for the version of z/OS that is running on your system for more information about the IWMECREA Workload Management Service and the EXSTARTDEFER parameter. Data Type String Default YES APAR PM24445 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.37 of WebSphere Application Server V6.1. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM24445
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-10-13
Closed date
2011-01-07
Last modified date
2011-05-02
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 FOR Z
Fixed component ID
5655I3500
Applicable component levels
R610 PSY UK65883
UP11/04/06 P F104
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
25 October 2021