Hi, I need to stress test a server running Java Servlets, JMeter should be ideal. With these Servlets, there is a very standard login/out system in place for users of the system. For example, to get to any of your records on the server, you must Log in though LoginServlet from which you can then go to the other servlets. Very standard stuff.
However, with JMeter, with even the most simple test plan, a login consistently takes over 15 seconds. The login is done exactly as the browser does it (verified using BadBoy to capture everythng and then exported to JMeter), but JMeter sits and waits after posting the login information for over 15 seconds - and it just does not make any sense. I haev also tried without the BadBoy generated file, it threw up exactly the same problem. It's not the servers at fault. It's running Apache 2 on Solaris. This 15 second delay isn't replicable in any browser. Additionally, I captured the packets JMeter was sending and resent them raw over telnet exactly, but there was no 15 second delay. It seems to be something totally internal to JMeter. How can I address this? JMeter is my only option for stress testing, but this 15 second delay on *every* login is rendering it useless. Any ideas? Thanks for you time, Duncan Frostick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
