Thanks you for the replies, Got it to work by creating an extension; I created a JavaSampler that extended org.apache.jmeter.protocol.java.sampler.AbstractJavaSamplerClient and started a thread, then proceeded with the rest on the test . Since the context is created using a singleton class, ones needs take into account that variables can be changed by other nodes in the test. Regards
Sipathamandla Shoko Software Developer Dariel Solutions - http://www.dariel.co.za ____________________________________________________________________________________________ 2008/11/5 sebb <[EMAIL PROTECTED]>: > On 05/11/2008, Nair, Pramod <[EMAIL PROTECTED]> wrote: >> Yes >> >> When you share Host Name etc you are declaring them as Global Variables >> in "Test Plan" > > Misleading; there are no global variables. Test Plan variables (and > UDVs) are made available to all threads, but they are not shared, they > are just the initial values for all threads. They are seen globally, > but each thread gets its own copy. > >> Chk this link - >> http://www.nabble.com/how-do-I-pass-a-value-obtained-in-%22Thread-Group- >> 1%22-%28with-%22XPath-Extractor%22-from-a-%22WebService%28SOAP%29-Reques >> t%22%29-to-%22Thread-Group-2%22-for-use-as-input-to-%22WebService%28SOAP >> %29-Request%22-to19683794.html#a19686226 >> > > Not easy to follow. The important bit is to use something like > > ${__setProperty(sessionid,${theId}}; > > after extracting the session id > > Then refer to it in the other thread as > > ${__P(sessionid)} > > JMeter threads are intended to represent individual users, which is > why the variables are not shared, and why passing data between threads > is not easy - it should rarely be necessary. > > JMeter also does not support concurrent samples in a single thread. > It was not designed that way; in most cases sequential samples will do > just as well. > > For example, in this case, when the original page has been loaded, > just run the poll until it is complete. > > This is mostly what the browser would do anyway; a browser cannot > start running the background poll until at least some of the page has > been loaded and interpreted. > >> >> >> -----Original Message----- >> From: Sipathamandla [mailto:[EMAIL PROTECTED] >> >> Sent: Wednesday, November 05, 2008 3:57 PM >> To: JMeter Users List >> Subject: Re: Threads Running Concurrently >> >> Thanks for the reply. >> >> I have already shared certain variables for all threads, like host and >> context. >> >> Is it possible to share such information like session details of a >> logged in >> user? >> >> Kind Regards >> >> Sipathamandla Shoko >> Software Developer >> Dariel Solutions - http://www.dariel.co.za >> >> >> ________________________________________________________________________ >> ____________________ >> >> >> >> 2008/11/5 Nair, Pramod <[EMAIL PROTECTED]> >> >> > You can share variable between threads using JMeter properties. >> > This has been discussed previously. You can check the archive. >> > >> > >> > -----Original Message----- >> > From: Sipathamandla [mailto:[EMAIL PROTECTED] >> > Sent: Wednesday, November 05, 2008 2:44 PM >> > To: JMeter Users List >> > Subject: Re: Threads Running Concurrently >> > >> > Thanks for the reply. >> > >> > |_GlobalVariables (User Defined Variables) >> > |_AccountsCSV (CSV Data Set Config) >> > |__BasicOperations (Thread Group) >> > |__login (http request) >> > |__CheckUpdates(Loop) - loop forever until test ends >> > |__Delay (1min timer) >> > |__checkForUpdates (http request) >> > |__placeAnOrder (http request) >> > >> > What i wanted to achieve was a way to start the CheckUpdates loop, >> leave >> > it >> > looping and proceed with a the next node, placeAnOrder. I could have >> > used >> > multiple threads, one thread looping, one placing the order, but the >> > application does not allow multiple user sessions (sessions variables >> > are >> > not shared across threads, please correct me if i'm wrong) >> > >> > Is there a way to achieve this? >> > >> > Sipathamandla Shoko >> > Software Developer >> > Dariel Solutions >> > 0860 DARIEL >> > >> > >> ________________________________________________________________________ >> > ____________________ >> > >> > >> > >> > 2008/11/5 Nair, Pramod <[EMAIL PROTECTED]> >> > >> > > The execution is always top down within a thread. >> > > But you can have different threads that work in parallel. >> > > >> > > You will need to uncheck "Run Thread groups consecutively" in the >> Test >> > > Plan where you create different threads. >> > > >> > > But I guess the thread groups start randomly not following the >> > top-down >> > > order. >> > > >> > > >> > > Thanks >> > > Pramod >> > > -----Original Message----- >> > > From: Sipathamandla [mailto:[EMAIL PROTECTED] >> > > Sent: Wednesday, November 05, 2008 2:09 PM >> > > To: [email protected] >> > > Subject: Threads Running Concurrently >> > > >> > > I have a web application that periodically polls the server for >> > updates >> > > in >> > > the background while the user is doing some action. I have seen that >> > > execution is sequential (correct me if i'm wrong) and if one create >> a >> > > loop >> > > controller, the execution will wait for the loop to complete before >> > > executing the next node. >> > > >> > > Is there starting a thread, in this case a loop and continue with >> the >> > > next >> > > nodes. >> > > >> > > Any help welcome. >> > > >> > > >> > > The information contained in this transmission may contain >> privileged >> > and >> > > confidential information and is intended only for the use of the >> > person(s) >> > > named above. If you are not the intended recipient, any review, >> > > dissemination, distribution or duplication of this communication is >> > strictly >> > > prohibited. If you received this email in error, please contact the >> > sender >> > > immediately by reply e-mail and destroy all copies of the original >> > message. >> > > This email is not intended as an offer or solicitation for the >> > purchase or >> > > sale of any financial instruments. >> > > >> > > >> --------------------------------------------------------------------- >> > > 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] >> >> > > --------------------------------------------------------------------- > 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]
