Return-Path: X-Original-To: apmail-jmeter-user-archive@www.apache.org Delivered-To: apmail-jmeter-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 84273DECB for ; Mon, 11 Mar 2013 16:28:46 +0000 (UTC) Received: (qmail 8962 invoked by uid 500); 11 Mar 2013 16:28:46 -0000 Delivered-To: apmail-jmeter-user-archive@jmeter.apache.org Received: (qmail 8746 invoked by uid 500); 11 Mar 2013 16:28:45 -0000 Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "JMeter Users List" Delivered-To: mailing list user@jmeter.apache.org Received: (qmail 8711 invoked by uid 99); 11 Mar 2013 16:28:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Mar 2013 16:28:44 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of asp.adieu@gmail.com designates 209.85.219.44 as permitted sender) Received: from [209.85.219.44] (HELO mail-oa0-f44.google.com) (209.85.219.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Mar 2013 16:28:37 +0000 Received: by mail-oa0-f44.google.com with SMTP id h1so4744113oag.31 for ; Mon, 11 Mar 2013 09:28:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=CYbz+ScorabforvJTWbJOqHUqd9Tjn8Gt6K3BhICAF0=; b=hgP0VOBma6yYQj8Fb55p4egVwk+gmK9nbrg3K58NXE5+dmNMrCGNOCzjlO8/ZAR8xy trIEnhf4be4NpZwenzEk/dYZ7Z7BqxicGMrBnR+CbeK3SPt65+u31YKMmkY4uFmuaLYi bJVu3Kz+fV2DevcO2FCzOly3B76XzDhn8pshRFVI4wPMEMwm/5/KDzcDk6odE7Grun+o CPdK7xArThTVYUCY5QTsRKzU2FnuJUY/J6aTI7vYcs9+0QjuYMKG9sUQdjibmpI0uDUF eadMiOy3LwEkhnPdlc7FLt3aeY646hzr/W50ytpvvYcGc9XYlPGgqZC9IHBgDuecK1iD e6GA== MIME-Version: 1.0 X-Received: by 10.60.6.133 with SMTP id b5mr9101062oea.81.1363019296691; Mon, 11 Mar 2013 09:28:16 -0700 (PDT) Received: by 10.76.82.98 with HTTP; Mon, 11 Mar 2013 09:28:16 -0700 (PDT) In-Reply-To: References: Date: Mon, 11 Mar 2013 18:28:16 +0200 Message-ID: Subject: Re: Persist JSESSIONID throughout a TestPlan From: Adrian Speteanu To: JMeter Users List Content-Type: multipart/alternative; boundary=e89a8fb20334005c8f04d7a8a96b X-Virus-Checked: Checked by ClamAV on apache.org --e89a8fb20334005c8f04d7a8a96b Content-Type: text/plain; charset=UTF-8 This question has been asked before, but I don't remember a time it has been solved. You'll want to create a variable in one of the thread group, such as "variable_" and then all other threads will be able to reference it. Of course, you'll need to make thread groups with an equal number of threads. Creating the variable is easy, but making it accessible to the other threads was not possible in older version (? maybe I'm mistaken about this, but I looked to implement this particular use-case 3 years ago and found no solution). However, with the versions released in the last couple of years, you have the beanshell server that can help with this. I haven't tested it yet, its in my to do list, but I think someone explained how it can be used to update a variable from within multiple threads, the same principle should apply in your use case. Also, there is a plugin: http://code.google.com/p/jmeter-plugins/wiki/InterThreadCommunication, that might do the job, but again, haven't had the time to use it myself. So you're use-case is doable, but you should be double-careful :) and test that what you think you are doing is actually what is happening. With thread sharing and concurrency you can easily run into weird situations (i'm thinking other values than expected, but memory leaks aren't excluded either). Good luck with this. Also, please be kind and let us know what solution you used in the end. I think you should appreciate how useful this contribution might be for someone else. Thanks, --Adrian S On Mon, Mar 11, 2013 at 1:48 PM, Alaka P A wrote: > I have to test the webserver which has to maintain sessions. > For this purpose I need to maintain session ids in jmeter. > It has been working for ThreadGroup as I > am using HTTP Cookie Manager for every Thread Group. > But i want to use the same > JSESSIONID across the test plan which includes several Thread Groups. > Not able to achieve this. > I tried using HTTP Cookie Manager globally for a Test Plan, > But it didnt work. > I am using jmeter 2.5 version. Can anybody help me with this? > Thanks ! > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org > For additional commands, e-mail: user-help@jmeter.apache.org > > --e89a8fb20334005c8f04d7a8a96b--