Issue 3586: Server-side thread-scoped PICurrent to request-scoped PICurrent problem (interceptors-rtf)
Source: International Business Machines (Mr. Russell Butek, )
Nature: Uncategorized Issue
Severity: 
Summary: In document ptc/00-03-03, page 21-35, point 5 states:

5. The ORB logically copies the RSC to the server-side TSC after the
receive_request_service_context points are processed and before the servant
manager is called. >>>>>This TSC is within the context for both the
invocation of the
servant manager and the invocation of the target operation.<<<<< The
receive_request
points may modify the RSC, but this no longer affects the TSC.

I've bracketed the questionable sentence between >>>>> <<<<<.  The problem
arises in point 8:

8. The TSC is copied back to the RSC, overwriting the slots in the RSC.

WHICH thread-scoped current is copied back to the request-scoped current?
We have at least 2 threads to worry about - the servant manager thread and
the target operation thread - and these could themselves spawn other
threads.  Which current is supposed to be copied back to the request?

I suggest the following change to point 8:

8. The TSC from the thread on which the ORB invoked the target operation is
copied back to the RSC, overwriting the slots in the RSC.

Resolution: In document ptc/00-04-05, make the recommended change.
Revised Text: Replace the text in bullet 8 in section 21.4.4.5 Flow of PICurrent between Scopes: 

8. The TSC is copied back to the RSC, overwriting the slots in the RSC. 

with: 

8. The TCS from the thread on which the ORB invoked the target operation is copied back to the RSC, overwriting the slots in
the RSC. 

Actions taken:
April 27, 2000: received issue
January 9, 2001: closed issue
Discussion: 

End of Annotations:=====
From: butek@us.ibm.com
Received: from southrelay02.raleigh.ibm.com
(southrelay02.raleigh.ibm.com [9.37.3.209])
			      by e22.nc.us.ibm.com (8.9.3/8.9.3) with
			      ESMTP id IAA23888;
			      Thu, 27 Apr 2000 08:20:29 -0500
Received: from d54mta08.raleigh.ibm.com (d54mta08.raleigh.ibm.com
[9.67.228.40])
	by southrelay02.raleigh.ibm.com (8.8.8m3/NCO v2.07) with SMTP
	id IAA93524;
	Thu, 27 Apr 2000 08:39:49 -0400
Received: by d54mta08.raleigh.ibm.com(Lotus SMTP MTA v4.6.5  (863.2
5-20-1999))  id 852568CE.00458A3B ; Thu, 27 Apr 2000 08:39:33 -0400
X-Lotus-FromDomain: IBMUS
To: issues@omg.org, interceptors-ftf@omg.org
Message-ID: <852568CE.00457FBA.00@d54mta08.raleigh.ibm.com>
Date: Thu, 27 Apr 2000 07:29:33 -0500
Subject: Server-side thread-scoped PICurrent to request-scoped
PICurrent
	 problem
Mime-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain; charset=us-ascii
X-UIDL: 'hi!!g=I!!P+_!!mVo!!



In document ptc/00-03-03, page 21-35, point 5 states:

5. The ORB logically copies the RSC to the server-side TSC after the
receive_request_service_context points are processed and before the
servant
manager is called. >>>>>This TSC is within the context for both the
invocation of the
servant manager and the invocation of the target operation.<<<<< The
receive_request
points may modify the RSC, but this no longer affects the TSC.

I've bracketed the questionable sentence between >>>>> <<<<<.  The
problem
arises in point 8:

8. The TSC is copied back to the RSC, overwriting the slots in the
   RSC.

WHICH thread-scoped current is copied back to the request-scoped
current?
We have at least 2 threads to worry about - the servant manager thread
and
the target operation thread - and these could themselves spawn other
threads.  Which current is supposed to be copied back to the request?

I suggest the following change to point 8:

8. The TSC from the thread on which the ORB invoked the target
   operation is
copied back to the RSC, overwriting the slots in the RSC.

Russell Butek
butek@us.ibm.com