IBM Support

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

Fixes are available

7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
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.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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • RMI/IIOP interfaces generated for EJB 3.0 are not backward
    compatible, which might cause errors such as
    
    java.lang.OutOfMemoryError
    at com.ibm.rmi.iiop.CDRReader.readBytesForString
    (CDRReader.java:2279)
    at com.ibm.rmi.iiop.CDRReader.readStringOrIndirection
    (CDRReader.java:472)
    at com.ibm.rmi.iiop.CDRReader.read_codebase_URL
    (CDRReader.java:2852)
    at com.ibm.rmi.iiop.CDRReader.fast_read_value
    (CDRReader.java:1893)
    at com.ibm.rmi.iiop.CDRReader.read_value
    (CDRReader.java:2000)
    at com.ibm.example._EJB3_Stub.method(Unknown Source)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V7.0 and   *
    *                  V8.0 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:                                              *
    ****************************************************************
    EJB 3.0 allows remote business interfaces that do not extend
    java.rmi.Remote, but EJB container still uses IIOP stubs for
    these interfaces.  Because the interface is not considered to
    be an RMI abstract interface, these stubs would normally be
    marshalled using write_value, which means the ORB would not
    reconnect them when they are unmarshalled by a client using
    read_value.  To avoid this problem, stubs and ties generated
    by the EJB container always use write_abstract_interface and
    read_abstract_interface, which makes them incompatible with
    stubs and ties that are generated by rmic.
    

Problem conclusion

  • An option has been added that allows EJB container to generate
    stubs and ties that are compatible with rmic.  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: values
    This enables rmic-compatible use of read_value/write_value
    8. Select OK.
    
    To enable the fix in application clients, specify the
    following option when running the launchClient command:
    -CCDcom.ibm.websphere.ejbcontainer.rmicCompatible=values
    
    To enable the fix while generating stubs for thinclient
    environments, use the following option when running the
    createEJBStubs command:
    -rmic values
    
    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.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.21 and 8.0.0.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

    PM46698

  • 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

    2011-08-30

  • Closed date

    2011-09-16

  • Last modified date

    2011-09-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PM55677

Fix information

  • Fixed component name

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM46698

Modified date: 16 September 2011