We have a simple performance test in the application.
- We log in
- Search by some criteria
- repeats the search for various parameters.
We use Jmeter to test performance. We need to have multiple threads to test this in a scalable manner.
The way we currently have is:
-Test Plan - Thread Group - Cookie Manager - Login To application - Search on param 1 - Search on param 2 - results summary table - Summary report
Thus, we have a summary pivot table and a report at the plan level, while a cookie manager is present at the level of the stream group.
When I run for a single thread, it works fine and works fine. When I scale it to multiple threads, as soon as the next thread starts, the session for the last thread becomes invalid. This causes crashes for all already running threads due to a newly created thread.
I achieved this result with the observation:
1. If I run multiple threads, only the last thread has valid answers in the final result tree
2. If I start with 2 threads with a rise period of 10 seconds, which means that each thread takes time to finish itself, then both of them are successfully executed.
According to my understanding, each stream is registered in the application, and since the cookie manager is at the stream level, will the values ββbe maintained for the session identifier for each stream, respectively? But what causes the redefinition of the value of the session identifier between threads?
Any help would be greatly appreciated.
java cookies session-cookies session jmeter
Priyank Sep 07 '09 at 13:35 2009-09-07 13:35
source share