Help with Constant Timer and Listener, gradually Threads

Hello, im trying to load test a web application. Created a testplan, which requests my application. The user clicks trough a part of the site. (12 HTTP Request Sampler) My Question: Is it neccessary to add a constant Timer between each request? My secons Question: Is it possible to send for

Re: Help with Constant Timer and Listener, gradually Threads

1st question: The timer is not required, but it's handy if you need to simulate think time. If you're doing scalability testing you may want think time If you're doing a stress test, you probably will not want think time, it will depend on what your server can handle, performance reqs. etc...

Re: Hot to stop http request execution in case of no response

In JMeter 2.3.3 you can set a response timeout in the HTTP Request, or HTTP Request HTTPClient nodes. JMeter 2.3.3 release notes: HTTP Samplers now support connection and request timeouts (requires Java 1.5 for Java Http sampler) If this doesn't suit your needs, you could use a beanshell

Re: Help with Constant Timer and Listener, gradually Threads

Of course. I want to simulate 5000 virtual Users (Threads) on my application. The way i want to do this, is not to start all 5000 of them within a specific time. My imagination to make this possible with distributed testing. I've got 17 computers. 16 slaves, 1 master. The master gets the

Re: Hot to stop http request execution in case of no response

Tony, thanks a lot! -- View this message in context: http://www.nabble.com/Hot-to-stop-http-request-execution-in-case-of-no-response-tp24019369p24034993.html Sent from the JMeter - User mailing list archive at Nabble.com. -

Re: Help with Constant Timer and Listener, gradually Threads

The following will work for either scenario, if you want to step-up in increments of 500, or gradually ramp up to 500, run at 500 for a specified amount of time, then gradually add 500 and so-on. - Use 10 thread groups, each with 500 threads, and set the startup delay equal, or greater than

Re: Regular Expression Extractor and its Variables

I agree that would be more efficient to do all assertions useing BeanShell I have never used Controllers, not sure why would that be a better way? Thanks, mattlamignat hi if you have a simple text match then BeanShell Assertion(or java or bsf) even if you have regexes you could use the java

Re: Help with Constant Timer and Listener, gradually Threads

Thank you very much. Thats what i'm looking for. I've booked a room in the university. All of the computers inside having the following data: - Pentium IV - 2.6GHz - 1GB Ram - Windows XP Sp3 Hope this will be enough to get a realistic result. -- View this message in context:

Re: Regular Expression Extractor and its Variables

independent of number of assertions to be made, more descriptive without needing to read the code regards deepak On Mon, Jun 15, 2009 at 11:29 AM, mattlamignat mateusz_grode...@o2.plwrote: I agree that would be more efficient to do all assertions useing BeanShell I have never used

expected Response code: 500

I'm getting 'Response code: 500' responces for several SOAP/XML-RPC requests and they are expected responses. How I can force JMeter to not mark such responces as failures. I mean marked as red transactions in 'View Results Tree' -- View this message in context:

Re: expected Response code: 500

In the Response Assertion check the ignore response box and add an assertion for response code equals 500 Regards, Noel - mattlamignat mateusz_grode...@o2.pl wrote: I'm getting 'Response code: 500' responces for several SOAP/XML-RPC requests and they are expected responses. How I

Re: expected Response code: 500

hi Can you try to put in a response assertion and assert that response code should be 500, regards deepak On Mon, Jun 15, 2009 at 11:34 AM, mattlamignat mateusz_grode...@o2.plwrote: I'm getting 'Response code: 500' responces for several SOAP/XML-RPC requests and they are expected responses.

Re: Regular Expression Extractor and its Variables

I agree. BeanShell is easy to setup, the scripts are relatively easy to debug and you can do [almost] anything with them. The problem with regular expressions is that you might get them to work but you can't be sure when they are going to fail. On the other hand there are tools that help write

Re: Regular Expression Extractor and its Variables

Try: - vars.get(city_10) or you could use ${city_10} - vars.put( city_10, a ) - print(${city_10}) or print(vars.get(city_10)) On Fri, Jun 5, 2009 at 12:19 PM, mattlamignat mateusz_grode...@o2.plwrote: This is my test plan: |-User Defined Variable |-HTTP Request |-Regular