Thanks, but I think I did not explain myself clear enough.
The session is set up by opening a TCP connection and sending a login request. From that point on, all transactions (both from the server and from the client) are sent on that same connection (=same socket). I suspect Jmeter was build with HTTP in mind and a symmetrical protocol (e.g., TCP) challenges its design.
Any help on this please?

----- Original Message ----- From: "Christian Baumgartner" <[EMAIL PROTECTED]>
To: "'JMeter Users List'" <[email protected]>
Sent: Thursday, July 21, 2005 9:27 AM
Subject: AW: TCP session


Maybe you want to use the URL REWRITE MODIFIER that stores the session ID
and replaces it in every request. (if you use session id in you r URL.. Else
there is the posibility to use the cookie manager that fetches the cookies,
and you can use them as normal variables for assertions ..

Maybe you specify in more detail how the session is set up, what method is
used (think it is a session).


-----Ursprüngliche Nachricht-----
Von: Zohar Amir [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 21. Juli 2005 07:16
An: [email protected]
Betreff: TCP session


Hi,
I need to emulate a client's behavior with Jemeter. The client connects to
the server via TCP. The connection is set up on login and kept throughout
the session, where transactions are exchanged with the server. Any way of
doing his with Jmeter? I probably need to open a TCP socket on
startup and use this same socket for all transactions. I also need a thread
listening on the socket for incoming transactions.
Thanks,
Zohar.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to