IBM Support

PI09894: WLM CLASSIFICATION OF IIOP WORK REQUESTS NOT WORKING

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • All incoming IIOP work requests are classified by the
    component_name (EJB name) of the first
    <iiop_classification_info> tag even though there is a workload
    mix with different component_name (EJB name) specified in the
    wlm_classification_file.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 z/OS WLM Workload               *
    *                  Classification with OSGi EJB applications.  *
    ****************************************************************
    * PROBLEM DESCRIPTION: z/OS WLM Workload Classification        *
    *                      classifies all IIOP work requests       *
    *                      by name of first EJB request            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using EJB OSGi applications with z/OS WLM Workload
    Classification, the following exception occurs:
    IllegalArgumentException while parsing j2eeName;
    java.lang.IllegalArgumentException: Unsupported EJB Type: 49
    at
    com.ibm.ws.ejbcontainer.EJBOAKeyImpl.<init>(EJBOAKeyImpl.java:19
    7)
    at
    com.ibm.ws390.orb.BOSSObjectKey.getAMC(BOSSObjectKey.java:1202)
    at
    com.ibm.ws390.orb.ClassificationParserImpl.classifyIIOP(Classifi
    cationParserImpl.java:675)
    at
    com.ibm.ws390.channel.ziop.ORBServiceContextFilter.classifyReque
    st(ORBServiceContextFilter.java:425)
    at
    com.ibm.ws390.ziop.ZIOPMessagePlugin.processIncomingContext(ZIOP
    MessagePlugin.java:282)
    at
    com.ibm.ws390.ziop.ZIOPChannelBridge.filterInbound(ZIOPChannelBr
    idge.java:465)
    at
    com.ibm.ws390.ziop.ZIOPCPPUtilities.process_inbound_request(Nati
    veMethod)
    This does not cause an immediate failure, but all IIOP work
    requests will be classified by the first EJB request.
    

Problem conclusion

  • Code used by the WLM Classification feature was never
    updated for the new OSGi application/module versioning
    support that was added in v8.5.
    
    For modules with this new versioning support enabled
    additional information is encoded in the EJB Type byte
    of the servant key. This is not being accounted for
    during WLM classification.
    
    A fix has been provided so that versioned EJB modules
    will be properly classified.
    
    APAR PI09894 is currently targeted for inclusion in
    Service Level (Fix Pack) 8.5.5.3 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 number

    PI09894

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-17

  • Closed date

    2014-03-05

  • Last modified date

    2014-03-05

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022