PI24580: INCORRECT COUNTS WHEN USING WLM CLASSIFICATION FILE

8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• When using a wlm classification file, the transaction class
  assigned to the first <iiop_classification_info> tag counts
  about double amount of EJB calls than there really are.  This
  happens because of the way IIOP classification of CORBA objects
  is done.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5 for z/OS                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: IIOP classification of CORBA objects    *
  *                      end up matching the first IIOP          *
  *                      classification rule in the              *
  *                      classification file that does           *
  *                      not explicitly filter using             *
  *                      method_name or                          *
  *                      activity_workload_classification.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  IIOP classification of CORBA objects end up matching the first
  IIOP classification rule in the classification file that does
  not explicitly filter using method_name or
  activity_workload_classification because CORBA objects do not
  have any sensible application_name, module_name or
  component_name.
  

Problem conclusion

• Changed the code to use new InboundClassification element
  attributes when classifying IIOP CORBA requests.
  The three new optional InboundClassification element attributes
  are default_iiop_application_name, default_iiop_module_name and
  default_iiop_component_name. These new attributes can be used
  to either avoid matching existing IIOP classification rules,
  or define a IIOP classification rule that matches the new
  values. The new rule can be used to set a specific transaction
  class for CORBA requests.
  
  APAR PI24580 is currently targeted for inclusion in Fix Pack
  8.5.5.5 of WebSphere Application Server V8.5.
  
  Please refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  
  In addition, please refer to URL:
  http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack PTF information.
  

Temporary fix

Comments

APAR Information

• 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

• R850 PSY

     UP