The second observation: two requests to the same servlet always handled serially. Tomcat normally creates one instance of a servlet for every declaration in web.xml. The exception is SingleThreadModel (deprecated, don't use this) servlets. There's no provision in tomcat to create more instances as the load on the server increases (maybe there is such a provision and I've missed it?). Instead, the processing threads should call the servlet methods in parallel. I'm not sure why you're not seeing this behavior, perhaps someone else could comment, as I have to run to a meeting ;)
Yoav Shapira
Yes - All you mentioned per Servlet spec expected behavior - why I was surprised at what I was seeing. I have additional qualification data but
believe I should post under a new thread / subject appropriate. -Jim Layer-
egg-on-face update:
Wasn't controlling my variables closely enough. Weird non-concurrent
behavior I observed was confined to brower-based tests. Screwed up
on the earlier multi-instance client test tool exercise - works as
expected when I'm explicitly controlling client behavior (headers, etc.).
Thanks (Yoav) again for your help,
Regards,
-Jim Layer-
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
