Cookie Handling SoapUI Runner
I believe I may have a series of bugs, and or mistakes on my part. We have a soapui 4.5 TestCase that works multithreaded within SoapUI because it appears that SoapUI is not respecting the "Maintain ...
Forum Discussion
The thing that concerned me most is that I assumed "Maintain Session" was on a "thread" and not on a "client" (ie loadui agent would be a single client but simulating many clients on separate threads). What I was seeing with many threads executing the same TestCase on loadui the session was passed between threads which never seems right. If a session is maintained for a client thread of execution would be fine (provided it can be turned off as well) but maintaining a the same HttpState object (I don't know HttpClient 4.0 but for 3.x this was the state object) between threads seems wrong regardless of the application respecting the "maintain session" configuration. Am i wrong about my understanding of the bug?