Re: Dynamic Parameter passing.

2013-03-16 Thread Nameet Jain
Thanks Deepak


On Fri, Mar 15, 2013 at 7:04 AM, Deepak Shetty shet...@gmail.com wrote:

 hi
 if this is the only case you could use something like
 If controller (check condition under which you send 2 params)
 +Http request
 If controller(check condition under which you send 2 params)
 +http request

 If you have too many variations then you can use the api to add parameters
 - an example of which is here
 http://theworkaholic.blogspot.com/2010/03/dynamic-parameters-in-jmeter.html

 The link shows one value being added dynamically but you are free to add
 whatever you want using whatever conditions.

 regards
 deepak


 On Fri, Mar 15, 2013 at 2:19 AM, Nameet Jain jnam...@gmail.com wrote:

  Hello,
 
  I am using Jmeter for the first time and its great.
 
  My requirement is to capture the parameters from the http response and
 pass
  them to the next HTTP request. But the number of parameters here are
  dynamic (i.e. sometimes there will be 2 parameters to pass and some time
 10
  parameters.).  I am not getting how to manage dynamic number of
 parameters
  to pass with HTTP request.
 
  Any assistance is highly appreciated.
 
  --
  Thank you
  Nameet
 



Re: Unable to record using HTTP Proxy Server

2013-03-16 Thread Robin D. Wilson
I have a feeling we are not communicating clearly... Does your system work from 
the browser to the IIS server when the JMeter proxy is not used?

If it does, please setup the JMeter proxy, start it, and send pictures of the 
JMeter setup (while it is running) and the browser's proxy configuration, and 
what you see on the browser when you make a request to the IIS server with the 
proxy enabled... Also, send you JMeter log file...

--
Robin D. Wilson
VOICE: 512-777-1861



On Mar 16, 2013, at 12:49 AM, Rohit Soni rohit.s...@hqcc.sahara.co.in wrote:

Hi Robin,

I have re-verified that the browser is making the request to IIS server with 
both the ports 80  8080.

Thanks and Regards,

Rohit Soni

-Original Message-
From: Robin D. Wilson [mailto:rwils...@gmail.com] 
Sent: 15 March 2013 20:21
To: JMeter Users List
Cc: JMeter Users List
Subject: Re: Unable to record using HTTP Proxy Server

So can you verify for me that the browser can make requests to the IIS server?

--
Robin D. Wilson
VOICE: 512-777-1861



On Mar 14, 2013, at 11:13 PM, rohit.s...@hqcc.sahara.co.in wrote:

Yes Robin, the case is actually as mentioned by you

Browser and JMeter on the same machine
IIS and ASP (.NET) together on separate machine from browser Oracle on third 
machine

Regards,
Rohit Soni



 Based on your diagram, I can't tell if you are running JMeter on the 
 same machine as the browser (end user). Can you please clarify if this 
 is the case?
 
 Browser and JMeter on the same machine IIS and ASP (.NET) together on 
 separate machine from browser Oracle on third machine
 
 You need to verify that our browser can make requests to your IIS 
 without the proxy enabled.
 
 
 
 --
 Robin D. Wilson
 VOICE: 512-777-1861
 
 
 
 On Mar 14, 2013, at 1:31 AM, Rohit Soni 
 rohit.s...@hqcc.sahara.co.in
 wrote:
 
 1- Browser (used to make requests for URLs) We are using IE 9 and 
 Mozilla 5.0
 
 2-  JMeter Proxy
 
 We are having HTTP Proxy Server ? Global Settings ? 8080
 
 3- Web Server:- IIS 6
 
 4- App Server:-  ASP using .NET framework
 
 5- Database Server:- Oracle 11g
 
 Attached is the architecture for accessing the app through servers.
 
 Thanks and Regards,
 
 Rohit Soni
 
 
 -Original Message-
 From: Robin D. Wilson [mailto:rwils...@gmail.com]
 Sent: 13 March 2013 18:15
 To: JMeter Users List
 Cc: JMeter Users List
 Subject: Re: Unable to record using HTTP Proxy Server
 
 There is no conflict between port 80 and port 8080, since they are 
 different ports. Also, the conflict would only exist if the process 
 listening to the port were on the same physical box as the JMeter 
 proxy process. So it sounds like we have some other sort of problem here.
 
 Can you give us some idea of all the physical boxes you have involved 
 here? You have the following processes listed already, are they on 
 the same box, or different boxes?
 
 1) browser (used to make requests for URLs)
 2) JMeter Proxy
 3) Web server
 4) Application server (PHP, Java, ASP, CGI, etc. based application 
 system)
 5) Database server
 
 Also, can your browser communicate with the Web server (and 
 Application
 server) without the JMeter setup? The idea of the JMeter Proxy is that 
 the browser will pass through the Proxy on the way to the 
 Web/Application server.
 
 More details about your complete setup will probably help us help you...
 Even the URL you are trying to hit will possibly give us a clue as to 
 the problem...
 
 --
 Robin D. Wilson
 VOICE: 512-777-1861
 
 
 
 On Mar 13, 2013, at 4:55 AM, Lokesh K Sharma
 lokesh.sha...@hqcc.sahara.co.in wrote:
 
 Hi Everyone,
 
 
 
 First of all thank you Robin for your help.
 
 
 
 Friends with the help of robin's 2nd point the problem got resolved 
 partially, Yes here in our organization we have a proxy server on port 
 80 so we decided to give a try by removing organizations internet 
 connection and used personal direct internet connection because that i 
 guess do not have any proxy settings.
 
 
 
 After using personal direct internet connection we changed the browser 
 connection settings as Auto-detect proxy settings for this network 
 and saved the browser settings. Now when we provided server name 
 jmeter.apache.org in Http request defaults and clicked on Start 
 button of HTTP Proxy Server after entering all required fields. It 
 provided us the results in View Result Tree (with green color sign 
 mean success/pass i guess) and created a record in Recording Controller.
 
 
 
 But now when we tried the same way to record internal website of my 
 organization (which i have to test finally), but we were not able to 
 do the same because the site we tried to access is on intranet and we 
 are using direct internet connection.
 
 
 
 As per discussion with a colleague we come to know as we have our own 
 proxy server on port 80 might be because of same we are unable to 
 access our internal sites by making localhost on port 8080 so we 
 tried as per Robin suggestion by making it localhost on