The ORB fully supports multi-threaded clients. All such clients will share the same
TCP connection to the server (if they are all talking to the same server), but the
TCP connection is protected with a lock to prevent interference between different
threads, so that only one thread at a time can write to the connection.
Each thread that sends a request ends up being blocked in the
CorbaResponseWaitingRoom until all replies (there can be more than one if a long
reply is fragmented) are received. The ORB transport is effectively IO event
driven on receiving messages, so there should be no concurrency problems, and
this has been tested extensively. I really doubt that this could be the problem.
I don't know much about the client side security framework: if the problem is there,
Ron or Tim may be able to help more.
[Message sent by forum member 'kcavanaugh' (kcavanaugh)]
http://forums.java.net/jive/thread.jspa?messageID=276372