I've got some groveling to do. I discovered the problem. Two Words. "Blame Microsoft" ;-\ The problem was never with the Apache SOAP server. It was the MS ASP client I was using that was queing the messages. Something in way IIS was initializing the SOAP connector would not allow multiple client requests out. When I moved the ASP pages to a different server all was well, go figure. So, Thanks to all those who offered suggestions. I did learn from the discussion generated on Scope, so it was not for nothing. Thanks again, 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. >> >
