IBM Support

PM94096: STUBS AND TIES GENERATED FOR EJB 3.0 ARE NOT COMPATIBLE WITH STUBS AND TIES GENERATED BY RMIC.

Fixes are available

8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
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

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Ejb's automatic stub generation introduced in EJB 3 is not
    properly "mangling" exception package names that contain IDL
    keywords, which causes an incompatibility
    when such exceptions are thrown from ties generated by RMIC,
    which is what ejbdeploy used for EJB 2.
    

Local fix

  • No work around at this time.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  Enterprise Java Beans (EJB) 3.0 with        *
    *                  remote interfaces.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Stubs and ties generated for EJB 3.0    *
    *                      are not compatible with stubs and       *
    *                      ties generated by rmic.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an exception is thrown by a remote method, the exception
    package name must be mangled.  The stubs and ties generated by
    the EJB container do not mangle exception package names, which
    causes incompatibilities with stubs and ties generated by rmic.
    

Problem conclusion

  • By default, stubs generated by the EJB container will accept
    both mangled and unmangled exception names, which allows the
    stubs to interoperate with ties generated by rmic or by EJB
    container.
    
    Additionally, the option introduced in PM46698 has been
    extended to allow EJB container to generate stubs and ties
    that are strictly compatible with rmic with respect to
    exception name mangling.  When this option is used, the stubs
    and ties that are generated will not be compatible with
    clients or servers that are not using this option.
    
    To enable the fix in application servers:
    1. Open the administrative console.
    2. Select Servers.
    3. Select Servers > Application servers > server_name.
    4. Under Server infrastructure, select Java and Process
    Management > Process Definition.
    5. Under Additional properties, select Java virtual machine >
    Custom properties > New.
    6. In the Name entry field, type:
    com.ibm.websphere.ejbcontainer.rmicCompatible
    7. In the Value entry field, type: exceptions
    This enables rmic-compatible mangling of exception names
    8. Select OK.
    
    To enable the fix in application clients, specify the
    following option when running the launchClient command:
    -CCDcom.ibm.websphere.ejbcontainer.rmicCompatible=exceptions
    
    To enable the fix while generating stubs for thinclient
    environments, use the following option when running the
    createEJBStubs command:
    -rmic exceptions
    
    Additionally, thinclient environments must be using a
    com.ibm.ws.ejb.thinclient or com.ibm.ws.ejbportable JAR from
    an installation with the fix installed.
    
    Finally, regardless of the environment being used, the
    compatibility option can contain multiple levels of
    compatibility.  For example, specifying "values,exceptions"
    would enable the fix for both PM46698 and this APAR.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.31, 8.0.0.8, and 8.5.5.2.  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

    PM94096

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-07-30

  • Closed date

    2013-08-14

  • Last modified date

    2013-08-14

  • 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

  • R700 PSY

       UP

  • R800 PSY

       UP

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

Document Information

Modified date:
27 April 2022