IZ21990: CORBA.NO_IMPLEMENT IN ZWAS IN MULTIPLE CLASSLOADER SETUP

APAR status

• Closed as program error.

Error description

• Error Message: Customer testcase scenario:
  Multiple classloader policy is set with the application having 3
  EJBs- EJB_A, EJB_B and EJB_C with
  EJB_A, EJB_B loaded on one classloader and EJB_C on a different
  Class loader.
  The failure occurs on this call path:
  EJB_A.methodA() -->
     EJB_B.methodB1() -->
         EJB_C.methodC() -->
                EJB_B.methodB2()
  This processing results in an org.omg.CORBA.NO_IMPLEMENT
  exception.
  Please note: this problem will be seen only on zWAS.
  .
  Stack Trace: Caused by: org.omg.CORBA.NO_IMPLEMENT: vmcid: 0x0
  minor code: 0 completed: No
  at
  org.omg.CORBA.portable.Delegate.releaseReply(Delegate.java:376)
  at
  org.omg.CORBA.portable.ObjectImpl._releaseReply(ObjectImpl.java(
  Compiled Code))
  t _EJB_B.methodB2(_EJB_B.java:663)
  ... 28 more
  .
  

Local fix

• N/A
  

Problem summary

• The NO_IMPLEMENTs were thrown as a the delegate was incorrectly
  determined as being disconnected due to a inter operation bug in
  baseORB-zWAS's ORB.
  

Problem conclusion

• This defect will be fixed in:
  1.4.2 SR12
  1.4.2 SR12 (z/OS 64-bit)
  1.4.2 SR12 (Linux AMD64)
  1.4.2 SR12 (Windows AMD64)
  5.0.0 SR9
  .
  The fix involves reworking the logic used to determine the
  "disconnected-ness" of a delegate so that the zWAS ORB's
  operation is taken into account.
  .
  To obtain the fix:
  Install build 20080718 or later
  

Temporary fix

Comments

APAR Information

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

  PK65824

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

  PK67512

Fix information

• Fixed component name

  JAVA 5 ORB

• Fixed component ID

  620500123

Applicable component levels

• R500 PSN

     UP