Upon reflection, the cause of the problem is really more process than anything else. This feature was allowed without adequate review and is now causing problems with testing. Jmeter might not be able to fix that, but testing with it did expose a process problem!
Probably the most correct solution would be to modify the application to print an error that the user is already logged in. Jmeter could detect that with a XPath or Regex postprocessor and retry until the system allows it to log in. We'll see if the intersection between ideal and real world allows for that! -- Bruce Ide flyingrhenqu...@gmail.com
