You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2002/06/01 02:15:58 UTC
DO NOT REPLY [Bug 9330] -
JMeter uses same cookie with different threads
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9330>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9330
JMeter uses same cookie with different threads
swaziloo@monkeymind.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
OS/Version|All |Windows NT/2K
Resolution|INVALID |
Version|unspecified |1.7Beta3
------- Additional Comments From swaziloo@monkeymind.com 2002-06-01 00:15 -------
I am testing a registration process that uses cookies to maintain session
(WebLogic). If I run a single thread, JMeter behaves as expected, and I get
normal results. If I turn up the number of threads, I start to see a
predictable error that seems to be related to cookie management.
The registration process has 2 steps. The first step records a unique string
submitted by the user in the session. The second step gathers all the user's
typical data (name, email, etc.) The error I am having is that the data
submitted is failing as it does not match the unique string from step 1 (in
other words, the step 1 unique string is getting paired with another thread's
step 2 data.) If I run 8 test machines simultaneously, I do not see the error,
if I run 8 threads simultaneously, I do.
I suspect that JMeter is not properly cloning the Cookie Manager and therefore,
all the threads are sharing one. I have not yet tried the patch offered by
ajslater@attbi.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>