Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@apache.org Received: (qmail 61945 invoked from network); 20 Dec 2001 13:24:55 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 20 Dec 2001 13:24:55 -0000 Received: (qmail 12489 invoked by uid 97); 20 Dec 2001 13:24:55 -0000 Delivered-To: qmlist-jakarta-archive-jmeter-user@jakarta.apache.org Received: (qmail 12461 invoked by uid 97); 20 Dec 2001 13:24:53 -0000 Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "JMeter Users List" Reply-To: "JMeter Users List" Delivered-To: mailing list jmeter-user@jakarta.apache.org Received: (qmail 12445 invoked from network); 20 Dec 2001 13:24:53 -0000 Date: Thu, 20 Dec 2001 14:24:49 +0100 From: Henrik Ridder To: JMeter Users List Subject: Re: how to deal with jsessionid cookie? Message-ID: <84200000.1008854689@stora.automateld.net> In-Reply-To: <1008806771.4346.14.camel@mothra> References: <1008806771.4346.14.camel@mothra> X-Mailer: Mulberry/2.1.1 (Linux/x86 Demo) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --On Wednesday, December 19, 2001 16:06:10 -0800 Nathan Fiedler wrote: > (this is the same problem as Michael had reported yesterday, but I'll > try to explain in my own words...) > > I'm trying to load test our Java-based server, which uses the Jetty > servlet engine. With JMeter running as the proxy to record my browser > requests, our server is getting the requests and returning the response > to the browser. JMeter is recording all of the requests. However, JMeter > seems to be ignoring the jsessionid cookie header and so the URLs in > subsequent requests all contain the jsessionid as a CGI parameter. I had > hoped that the jsessionid cookie header would be used instead of the > url-rewriting. I am guessing that I want to do this to avoid rewriting > all of the URLs of the recorded requests, right? > > My setup is as follows. I'm using JMeter nightly build for 12/19/01 > running on Sun's JDK 1.3.1_01 on Linux. with the following tree of > components: > > Root > +- Test Plan >| +- ThreadGroup (10 threads) >| +- Simple Controller >| +- HTTP Cookie Manager >| +- HTTP Header Manager >| - User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.16 i686) > +- WorkBench > +- HTTP Proxy Server > > The header for User-Agent is there in an attempt to get the cookies > working, per Henrik's response to Michael's question yesterday. I've > tried putting both the cookie manager and header manager under the > simple controller, but that made no difference. > I didn't run the script with the proxy. I just used this proxy to record a sample script. > After the first set of requests the cookie manager shows no cookies. > What's more, the User-Agent header I have specified is not making it to > our server. Our server is seeing "Java1.3.1_01" as the user agent. I > wonder if this is the problem. That's strange becasue when I added the User-Agent our webserver (Apache) recorded that. This is a sample from my jmx file Mozilla/4.79 [en] (X11; U; Linux 2.2.12 i386) User-Agent gzip Accept-Encoding I don't know how much help this is, but thats how I did it. Good luck /Henrik > > Thanks in advance for any tips. > > nathan > > > > -- > To unsubscribe, e-mail: > For additional > commands, e-mail: > -- To unsubscribe, e-mail: For additional commands, e-mail: