Hello, I encounter a rather strange behaviour involving JMeter (2.0.2 on JKD 1.4.2_05) and Tomcat (4.1.18.0). *Sometimes* in my load test the session is being invalidated after the login. With low load (<= 10 Threads) the tests run without problems. With higher loads all threads are successful with the first request (login) but some of them (about 15%) fail in the second request because of an invalid session. Investigating the requests and the responses I have concluded that 1. In threads that perform timely adjucent logins exactly the same sessionids are received. 2. When these threads perform the second request, they send another sessionid. These new sessionids differ from each other and do not belong to any earlier thread. Example (simplified): Thread sessionid in Login/Response Sessionid in CustomerSelect/request 1 101 101 (OK) 2 102 102 (OK) 3 103 500 (not OK) 4 103 (same as in #3) 600 (not OK) My questions: - What might be the cause of the identical sessionids for the different threads? Is it a know problem in either JMeter or Tomcat? - Why does JMeter send a fake sessionid? One idea was that the concurrent logins might count as one login trial because of the KeepAlive flag. I have turned the KeepAlive flag from the login request off, but this did not help. Does anybody have further ideas? Thanks in advance! Noam Paz P.S. Of course I use the cookie manager in my testplan and do not manipulate the sessionid in the testplan. -- Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
