POA threading - more details

Hi,

I've encountered a strange phenomenon related to POA threading: I have a 
multi-threaded client that issues synchronous (e.g. not oneway) requests to a 
collocated server. 
At first, I used a POA with a thread pool in the server, using ORBacus 
policies. Then, I decided that since the client is already multithreaded and 
each thread issues synchronous invocations, then I should use the client's 
thread to perform the collocated request inside the server as well, to save 
thread resources. I implemented this by switching the POA threading policy to 
dispatch_same_thread.
The problem is, I got a considerably lower throughput when using the client's 
threads than when using a separate thread pool for the POA. Seems as if an 
"outsider" thread is required to do some additional processing compare to a 
"home" thread.
Can you explain why?

PS: I'm using ORBacus for Java 4.1.3, JDK1.4.2, Linux
PPS: The client issues dynamic invocations (DII) - just synchronous, not 
deferred or oneway.

Redgards,
Erez Hadad
_______________________________________________
OB-Users Mailing List - [email protected]
http://mail.ooc.nf.ca/mailman/listinfo/ob-users
Visit our support FAQ before you send a message.
http://www.orbacus.com/faq/support.html