IZ96234: OBJECT_NOT_EXIST EXCEPTIONS ON SOME CONNECTIONS.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Error Message: Even when LocationServiceDaemon is up, locate
    request messages on some connections fail with OBJECT_NOT_EXIST
    exceptions.
    .
    Stack Trace: <OSB>12/3/09 18:12:41:308 CET<CSB> 0000001b ORBRas
          1 com.ibm.rmi.iiop.Connection doLocateRequestWork:2610
    ORB.thread.pool : 0 The following exception was logged
                                     org.omg.CORBA.OBJECT_NOT_EXIST:
    BAD_SERVER_ID (1) for 0x4a4d424900000..........  vmcid: IBM
    minor code: C02  completed: No
     at
    com.ibm.CORBA.iiop.ServerDelegate.locate(ServerDelegate.java:262
    )
     at com.ibm.rmi.iiop.ORB.locate(ORB.java:452)
     at com.ibm.CORBA.iiop.ORB.locate(ORB.java:1741)
     at
    com.ibm.rmi.iiop.Connection.doLocateRequestWork(Connection.java:
    2589)
     at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2472)
    at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2221)
     at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:65)
     at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498)
    .
    

Local fix

Problem summary

  • The problem is caused due to accepting connections before
    LocationServiceDaemon initialization is complete.
    

Problem conclusion

  • This defect will be fixed in:
    5.0.0 SR12 FP5
    .
    Logic of establishing/setting up connections is changed to
    resolve this timing issue.
    .
    To obtain the fix:
    Install build 20110314 or later
    

Temporary fix

Comments

  • The ORB initialization has been fixed to ensure that the ORB
    will not process any requests till the ORB is completely
    initialized.  Any call made at the this time will block until
    the ORB is initialized.
    
    Applications which register an interceptor and make a call to
    the ORB in the post_init of the interceptor and applications
    which call the ORB as part of plugin initialization will
    encounter problems.  According to the CORBA spec, the result of
    calling the ORB at this time is not defined, but applications
    may previously have run without reporting an error.  After
    applying this APAR, the applications will hang, because the
    calls to the ORB will block until the ORB is initialized, but
    the ORB will not initialize until the plugin initialization and
    post_init processing has completed.
    
    An application hanging because of this problem may be recognized
    as it will have a stack trace like this:
    
    at java/lang/Object.wait(Native Method)
    at java/lang/Object.wait(Object.java:199)
    at com/ibm/rmi/corba/ORB.getLSDPlugin(ORB.java:4598)
    at com/ibm/rmi/iiop/Connection.lsdInit(Connection.java:721)
    at com/ibm/rmi/iiop/Connection.<init>(Connection.java:772)
    at
    com/ibm/rmi/iiop/TransportManager.createORBConnection(TransportM
    anager.java:118)
    .. <Code added as part of the post_init functionality>
    at
    com/ibm/rmi/pi/InterceptorManager.runPostInit(InterceptorManager
    .java:217)
    at com/ibm/rmi/corba/ORB.initializeInterceptors(ORB.java:624)
    at com/ibm/CORBA/iiop/ORB.initializeInterceptors(ORB.java:1073)
    at com/ibm/rmi/corba/ORB.orbParameters(ORB.java:1357)
    at com/ibm/rmi/corba/ORB.set_parameters(ORB.java:1247)
    at com/ibm/CORBA/iiop/ORB.set_parameters(ORB.java:1681)
    at org/omg/CORBA/ORB.init(ORB.java:364)
    
    or
    
    at java/lang/Object.wait(Native Method)
    at java/lang/Object.wait(Object.java:199)
    at com/ibm/rmi/corba/ORB.getLSDPlugin(ORB.java:4598)
    at com/ibm/rmi/iiop/Connection.lsdInit(Connection.java:721)
    at com/ibm/rmi/iiop/Connection.<init>(Connection.java:772)
    at
    com/ibm/rmi/iiop/TransportManager.createORBConnection(TransportM
    anager.java:118)
    .. <Code added as part of the initialization of plugins>
    at com/ibm/rmi/CORBA/iiop/Orb.initializePlugins(ORB.java:1363)
    at com/ibm/rmi/corba/ORB.orbParameters(ORB.java:1357)
    at com/ibm/rmi/corba/ORB.set_parameters(ORB.java:1247)
    at com/ibm/CORBA/iiop/ORB.set_parameters(ORB.java:1681)
    at org/omg/CORBA/ORB.init(ORB.java:364)
    
    Customers detecting such a hang need to modify their code so
    that the ORB is not called before it is initialized.
    

APAR Information

  • APAR number

    IZ96234

  • Reported component name

    JAVA 5 ORB

  • Reported component ID

    620500123

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-09

  • Closed date

    2011-03-23

  • Last modified date

    2011-11-29

  • 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

    JAVA 5 ORB

  • Fixed component ID

    620500123

Applicable component levels

  • R500 PSN

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Runtimes for Java Technology
ORB

Software version:

5.0

Reference #:

IZ96234

Modified date:

2011-11-29

Translate my page

Machine Translation

Content navigation