Ahhh, Perhaps you're onto something, the configuration for each of the application components(Apache SOAP 2.2 and Tomcat 3.3) are out of the box defaults. I would be delighted to know where one configures the rpcrouter to NOT be single threaded. I apologize if this question is covered elsewhere. I guess It's simply a matter of not knowing what I don't know. ;-\
Thanks, Dave "Hansen, Richard" wrote: > Why would you expect it to block using application scope? If your methods > are not synchronized (which they probably should not be) I don't think they > block. The Apache SOAP scoping controls how many instances of a service > class are created and when they are created. Application equals one global > instance, request means one instance per request, session means one per http > session. > > I suppose it is also possible that his rpcrouter servlet has been setup to > use the single threaded servlet model. > > Rick Hansen > > > -----Original Message----- > > From: Guy McArthur [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, December 11, 2001 3:57 PM > > To: [EMAIL PROTECTED] > > Subject: RE: Is Apache SOAP a turnstile? > > > > > > > > I think he's saying if you call the sleep method in client A > > at time 0, > > then by client B at time +1 seconds. With application scope, > > you'd expect > > A to block B, correct? But without app scope it should not block. > >
