Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 28930 invoked from network); 2 Aug 2010 16:46:49 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Aug 2010 16:46:49 -0000 Received: (qmail 45455 invoked by uid 500); 2 Aug 2010 16:46:49 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 45304 invoked by uid 500); 2 Aug 2010 16:46:48 -0000 Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: 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 45296 invoked by uid 99); 2 Aug 2010 16:46:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Aug 2010 16:46:48 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of shettyd@gmail.com designates 74.125.82.172 as permitted sender) Received: from [74.125.82.172] (HELO mail-wy0-f172.google.com) (74.125.82.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Aug 2010 16:46:41 +0000 Received: by wyb40 with SMTP id 40so3656134wyb.31 for ; Mon, 02 Aug 2010 09:46:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=xbWjcXraLcJHsYAd2B8xEHQumpRxax7P0hICEnRh+8A=; b=JqS/0fYuMtk5NizLABAUn48PUm6oBMGoLwxnTlvpnkCFeqtfCv1FHTjPqlIfDK2ZfR Fj7QZah7jlEk1BxevIkSmim3ruSC8LjrztyQeHOiVy383wKPRBSJ0NuNtaDw+IBwOj8W K4qiy4PoP7x+CxmOC/qahwpucygiUtDbLXEH4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=SfIxyoLuZAKrtZFMkaZRuzq3py5lQjORnKbgy8zeZfD5ncSa1VQEWLhQ3lCFubyjjn C3uBGSj6PPDZ8EKt86fwWb3xvRz+vw/VRfAmUZvjy0/ef40WMLPFujJM06628BUhTKxy HwcpkCTItPaXekQpN2UUV6ko5QUpsD/viC9wI= MIME-Version: 1.0 Received: by 10.227.128.82 with SMTP id j18mr5197814wbs.36.1280767581220; Mon, 02 Aug 2010 09:46:21 -0700 (PDT) Received: by 10.216.86.14 with HTTP; Mon, 2 Aug 2010 09:46:21 -0700 (PDT) In-Reply-To: <56B587E7C40D2F43B54FDC1BA897AC6D011F1780@KS-EVS1.smi.sachsen.de> References: <56B587E7C40D2F43B54FDC1BA897AC6D011F1780@KS-EVS1.smi.sachsen.de> Date: Mon, 2 Aug 2010 09:46:21 -0700 Message-ID: Subject: Re: jmeter and webflow: How to get another execution-Parameter for every single thread From: Deepak Shetty To: JMeter Users List Content-Type: multipart/alternative; boundary=0016e65a0788b7f0cc048cd9f053 X-Virus-Checked: Checked by ClamAV on apache.org --0016e65a0788b7f0cc048cd9f053 Content-Type: text/plain; charset=ISO-8859-1 hi is this the first step? Do you have a cookie manager? Do you have follow redirects instead of redirect automatically? If not it sounds like your application has a bug that doesnt allow it to work under concurrent access. You can experiment with different (> 1 second diff between threads) ramp up times and see (if it starts working correctly then it probably is a problem with your app) regards deepak On Mon, Aug 2, 2010 at 7:20 AM, Leis, Matthias - SID-NLKM < Matthias.Leis@sid.sachsen.de> wrote: > Hi, > > I am currently testing a Spring Webflow Application. The URLs look like > http://localhost:8080/spring/main-flow?execution=e1s1 > The initial request is http://localhost:8080/spring/main-flow, which > responds with a HTTP Status Code 302 which redirects to > http://localhost:8080/spring/main-flow?execution=e1s1. > When I start my test with more than one thread, every thread gets the > same URLs. So the application doesn't really execute anything (e.g. > Database access) the second time the URL is called, but returns only the > stored views (because the URL is always the same). > > The behaviour using a browser is different. The first instance gets > http://localhost:8080/spring/main-flow?execution=e1s1, the second > instance gets http://localhost:8080/spring/main-flow?execution=e2s1 > (notice e2s1 instead of e1s1) and so on and the application really > executes database accesses, web service calls and so on. > > So my question is: Does anybody have an idea, how to achieve, that the > first thread gets e1s1, the second thread e2s1 and so on. > > Thanks, any help is appreciated! > > Regards, > > Matthias > > > --0016e65a0788b7f0cc048cd9f053--