[jacorb-bugs] [Bug 935] New: Exceptions thrown from a servant locator's preinvoke can mess up the POA context in co-located calls

[bugzilla-daemon at jacorb.org]

http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=935

           Summary: Exceptions thrown from a servant locator's preinvoke can
                    mess up the POA context in co-located calls
           Product: JacORB
           Version: 3.1
          Platform: Other
        OS/Version: FreeBSD
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: ORB
        AssignedTo: jacorb-bugs at lists.spline.inf.fu-berlin.de
        ReportedBy: xelah-jacorbbugzilla at xelah.com


1. Make a call to a JacORB server.
2. The server implements this call by making a co-located call which uses a
servant locator.
3. The servant locator (in our case) throws OBJECT_NOT_EXIST.
4. The original call deals with it appropriately (throwing an exception in our
case).
5. The client makes a new call to the server.
6. JacORB never invokes the request on the server side and never returns a
response, due (IIRC) to a NO_CONTEXT exception.

orb.getPOACurrent()._removeContext( Thread.currentThread() ); is called in
Delegate.java:2799 when the servant locator throws an exception. However, the
matching _addContext (line 2704) was never called because the exception occurs
before it.


-- 
Configure bugmail: http://www.jacorb.org/cgi-bin/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.