Hi , My testing scenario for Servlet goes like this: 1. Post a XML Document as per application specs to a URL 2. Servlet interacts with the back-end components and produce a workflow document in XML form. The simple HTTP Client Test using URLConnection works fine and servlet is capable of handling all relevant exceptions arising out of various semantic errors introduced in the input XML document I am using the same setup to simulate a multithreaded test stub using URLConnection in which case very erratic behaviour is exhibited as following 1. 15 requests submitted - only 11 served 2. 15 requests submitted - only 14 served 3. 15 requests submitted - all 15 served 4. 5 requests submitted - only 3 served 5. 5 requests submitted - all 5 served 6. 5 requests submitted - only 4 served I am puzzled. I have increased necessary database connections in the pool. I am not using any standard test setup like HTTPUnit (which I assume also will handle the test the same way - correct me if I am wrong) My webserver is Tomcat 4.1.24. Could there be any problem in the client stub or it could be a problem with the server? Rgds Muthu
0
