Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 38606 invoked from network); 25 Feb 2006 01:54:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Feb 2006 01:54:23 -0000 Received: (qmail 72568 invoked by uid 500); 25 Feb 2006 01:54:14 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 72488 invoked by uid 500); 25 Feb 2006 01:54:14 -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 72456 invoked by uid 99); 25 Feb 2006 01:54:13 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Feb 2006 17:54:13 -0800 X-ASF-Spam-Status: No, hits=0.9 required=10.0 tests=DNS_FROM_RFC_WHOIS,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [216.82.250.83] (HELO mail120.messagelabs.com) (216.82.250.83) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 24 Feb 2006 17:54:12 -0800 X-VirusChecked: Checked X-Env-Sender: poongs@att.com X-Msg-Ref: server-14.tower-120.messagelabs.com!1140832429!9487605!1 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [134.24.146.4] Received: (qmail 10379 invoked from network); 25 Feb 2006 01:53:49 -0000 Received: from unknown (HELO attrh2i.attrh.att.com) (134.24.146.4) by server-14.tower-120.messagelabs.com with SMTP; 25 Feb 2006 01:53:49 -0000 Received: from ACCLUST04EVS1.ugd.att.com (135.37.16.12) by attrh2i.attrh.att.com (7.2.052) id 43F8A544000F7385 for jmeter-user@jakarta.apache.org; Fri, 24 Feb 2006 20:53:49 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C639AE.521BDDC4" Subject: Require a mechanism to create random values across threads Date: Fri, 24 Feb 2006 20:53:48 -0500 Message-ID: <512EDCF0D09360488C6F52B085877FC205AAEF13@ACCLUST04EVS1.ugd.att.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Require a mechanism to create random values across threads Thread-Index: AcY5rlGBCCeGqXrcQ6OBvQcMVXiYaw== From: "Kalamegam, Poongundran \(Poongs\), ALABS" To: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C639AE.521BDDC4 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Hi, I am new to JMETER. I have been assigned the job of simulating JDBC requests to Oracle 10g. I have different kinds of JDBC requests based on a app group. We have 4 apps. I created 4 different thread groups. I have created JDBC requests under each of these thread groups. These write into a specific table which has unique constraints enabled. Now, i need to send a unique sessionid as part of the insert requests in JDBC Request Sampler. I tried to use session_id =3D = ${__threadNum()}-${__Random(100000,99999, myR)}. =20 I run around 30 threads for each of these thread groups.=20 =20 I am getting unique contraint errors for most of the requests as this session_id is same across the threads. Need your help in creating a session_id that would be unique across the threads and can be used forever. =20 Thanks, With Best Regards, Poongs. AT&T Labs Voice Applications, 214-452-1883 (Home) =20 "Get a good idea, and stay with it. Dog it, and work at it until it's done, and done right." - Walt Disney (1901-1966), American entrepreneur, movie producer and showman =20 This electronic message transmission, including any attachments, may contain information from AT&T that is proprietary and/or confidential. All Intellectual Property in this transmission, including any attachments is the sole property of AT&T. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this electronic transmission in error, please immediately notify the sender and destroy all material in its entirety, whether in electronic or hard copy format.=20 =20 ------_=_NextPart_001_01C639AE.521BDDC4--