Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-2423

ORBRunner uses the orb after run() returns


    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 5.2.0
    • Component/s: None
    • Labels:


      ORBRunner.java starts an orb using orb().run() but then performs operations on the orb after the run() method returns. According to the CORBA spec this is invalid:

      Once an ORB has shutdown, only object reference management operations(duplicate,
      release and is_nil) may be invoked on the ORB or any object reference obtained
      from it.

      Note that when the orb.run() method returns the orb has shutdown because, for the run method, the spec states:

      This operation will block until the ORB has completed the shutdown process,

      This issue has arisen because of a change made to our fork of the jdk orb: in the jdk orb shutdown method we join with all the orb runners. This results in deadlock:

      1. com.arjuna.orbportability.ORB.shutdown is a synchronized method and it calls shutdown on the jdk orb;
      2. shutdown on the jdk orb notifies the ORBRunner thread which now tries to call back into a synchronized method of com.arjuna.orbportability.ORB but is blocked because the monitor is held
      3. at this point the jdk orb shutdown would normally then return allowing the
        the ORBRunner thread to make progress but a recent change now means that the jdk orb shutdown method performs a join() on the various ORBRunner threads

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  tomekadamski Tomasz Adamski
                  mmusgrov Michael Musgrove
                • Votes:
                  0 Vote for this issue
                  4 Start watching this issue


                  • Created: