Remote Start

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Remote Start

Hohmann, Kurt D
Problem: Scripts work fine when run on the primary machine, but not when run from remote agents.

Background: I'm running a Windows Server (2008R2) with remote agents on RedHat Linux 6 machines. Everything is running JMeter at version 3.1. I've made appropriate and identical Hosts file entries on the Windows box and the Linux boxes, and verified that I can manually browse to my test site in all locations via browser. Linux boxes are running jmeter-server. All machines reside in the same domain.

Details: I'm using a Results Tree listener for troubleshooting. Pages appear to be working correctly (I'm seeing response code "200" in the Sampler result tabs) BUT - there is nothing displayed in any of the Response Data tabs. As I'm extracting  response data for login operations (e.g. JSESSIONID, VIEWSTATE), I'm never really getting logged in.

Any thoughts on further troubleshooting would be greatly appreciated.

Thanks,
Kurt


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Remote Start

glinius@live.com
This post has NOT been accepted by the mailing list yet.
As per JMeter Documentation:

mode
sample sending mode - default is StrippedBatch since 2.9. This should be set on the client node.
and

Stripped mode family strips responseData so this means that some Elements that rely on the previous responseData being available will not work.
This is not really a problem as there is always a more efficient way to implement this feature.
So it appears that you need to amend the "mode" property to something which doesn't contain "Stripped" in  order to make your correlation work. It can be done in 2 ways:

1. Add the next line to user.properties file on each remote slave:

mode=Standard
2. Passing the property value as command-line argument like:

jmeter -Jmode=Standard -s ......
See Apache JMeter Properties Customization Guide article for more information on using JMeter properties
pmd
Reply | Threaded
Open this post in threaded view
|

Re: Remote Start

pmd
In reply to this post by Hohmann, Kurt D
On Fri, Jan 20, 2017 at 8:01 PM, Hohmann, Kurt D <[hidden email]>
wrote:

> Problem: Scripts work fine when run on the primary machine, but not when
> run from remote agents.
>
> Background: I'm running a Windows Server (2008R2) with remote agents on
> RedHat Linux 6 machines. Everything is running JMeter at version 3.1. I've
> made appropriate and identical Hosts file entries on the Windows box and
> the Linux boxes, and verified that I can manually browse to my test site in
> all locations via browser. Linux boxes are running jmeter-server. All
> machines reside in the same domain.
>
Did you check connectivity between servers (jmeter-server <=> jmeter
client) ?

>
> Details: I'm using a Results Tree listener for troubleshooting. Pages
> appear to be working correctly (I'm seeing response code "200" in the
> Sampler result tabs) BUT - there is nothing displayed in any of the
> Response Data tabs. As I'm extracting  response data for login operations
> (e.g. JSESSIONID, VIEWSTATE), I'm never really getting logged in.
>

In distributed mode JMeter since 2.9 strips responses data for scalability.
If you need those for debugging, just put in user.properties:

mode=Standard

But switch back to default mode for your load test.

>
> Any thoughts on further troubleshooting would be greatly appreciated.
>
> Thanks,
> Kurt
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Cordialement.
Philippe Mouawad.
Reply | Threaded
Open this post in threaded view
|

RE: Remote Start

Hohmann, Kurt D
Thanks Philippe!

I was not aware of the 'mode=Standard' switch - I had skipped a few releases and never picked up on that one when I upgraded to 3.1. However, it's not working as I expected it to.

If I have that switch turned on in my user.properties, the script runs fine. The user is logged in, the responses look good, and the script completes without error.

As soon as I comment it out, the script fails at the point of login. I've tried this a few times with the same user data, same simple script, same jmeter client. It's as though the response data *has* to be reported back to the jmeter server in order for the HTTP URL Re-writing Modifier to pick up and apply the JSESSIONID.

It's a workaround to leave that item in place in user-properties, but based on what you said about it (and the fact that it's now shut off by default), I have concerns about the viability of a larger load test if that's in place.

Thanks,
Kurt


-----Original Message-----
From: Philippe Mouawad [mailto:[hidden email]]
Sent: Tuesday, January 24, 2017 2:29 PM
To: JMeter Users List <[hidden email]>
Subject: Re: Remote Start

On Fri, Jan 20, 2017 at 8:01 PM, Hohmann, Kurt D <[hidden email]>
wrote:

> Problem: Scripts work fine when run on the primary machine, but not
> when run from remote agents.
>
> Background: I'm running a Windows Server (2008R2) with remote agents
> on RedHat Linux 6 machines. Everything is running JMeter at version
> 3.1. I've made appropriate and identical Hosts file entries on the
> Windows box and the Linux boxes, and verified that I can manually
> browse to my test site in all locations via browser. Linux boxes are
> running jmeter-server. All machines reside in the same domain.
>
Did you check connectivity between servers (jmeter-server <=> jmeter
client) ?

>
> Details: I'm using a Results Tree listener for troubleshooting. Pages
> appear to be working correctly (I'm seeing response code "200" in the
> Sampler result tabs) BUT - there is nothing displayed in any of the
> Response Data tabs. As I'm extracting  response data for login
> operations (e.g. JSESSIONID, VIEWSTATE), I'm never really getting logged in.
>

In distributed mode JMeter since 2.9 strips responses data for scalability.
If you need those for debugging, just put in user.properties:

mode=Standard

But switch back to default mode for your load test.

>
> Any thoughts on further troubleshooting would be greatly appreciated.
>
> Thanks,
> Kurt
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Cordialement.
Philippe Mouawad.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
pmd
Reply | Threaded
Open this post in threaded view
|

Re: Remote Start

pmd
Hello Kurt,
If you're using HTTP_URL_Re-writing_Modifier, read the Manual :-) :
http://jmeter.apache.org/usermanual/component_reference.html#HTTP_URL_Re-
writing_Modifier

Could you give more details on why you use HTTP URL Re-writing Modifier, by
coincidence, I've just sent a proposal on dev mailing list to deprecated
(and remove) this element in future version so I'm interested to know how
it is used by users.

Here is an excerpt from discussion:

------------------------------------------------------------------------------------------------------------------------
What do you think of deprecating HTML Link Parser and HTTP URL Re-writing
Modifier?

   - I am not sure they are widely used
   - Their design does not suit well for performance as :
      - they require Previous Response, as a consequence, they do not work
      in Distributed mode
      - they use a Dom parser + Tidy
      - They are  based on old HTML parser so I don't think they work
   properly with new HTML 5 code
   - They suffer from old bugs:
      - https://bz.apache.org/bugzilla/show_bug.cgi?id=17252
      - https://bz.apache.org/bugzilla/show_bug.cgi?id=59943 => It was not
      reported on this element, but investigation showed it was affected

We could ask question on User mailing list and twitter to see if it's used.
------------------------------------------------------------------------------------------------------------------------


Regards
Philippe


On Wed, Jan 25, 2017 at 6:24 PM, Hohmann, Kurt D <[hidden email]>
wrote:

> Thanks Philippe!
>
> I was not aware of the 'mode=Standard' switch - I had skipped a few
> releases and never picked up on that one when I upgraded to 3.1. However,
> it's not working as I expected it to.
>
> If I have that switch turned on in my user.properties, the script runs
> fine. The user is logged in, the responses look good, and the script
> completes without error.
>
> As soon as I comment it out, the script fails at the point of login. I've
> tried this a few times with the same user data, same simple script, same
> jmeter client. It's as though the response data *has* to be reported back
> to the jmeter server in order for the HTTP URL Re-writing Modifier to pick
> up and apply the JSESSIONID.
>
> It's a workaround to leave that item in place in user-properties, but
> based on what you said about it (and the fact that it's now shut off by
> default), I have concerns about the viability of a larger load test if
> that's in place.
>
> Thanks,
> Kurt
>
>
> -----Original Message-----
> From: Philippe Mouawad [mailto:[hidden email]]
> Sent: Tuesday, January 24, 2017 2:29 PM
> To: JMeter Users List <[hidden email]>
> Subject: Re: Remote Start
>
> On Fri, Jan 20, 2017 at 8:01 PM, Hohmann, Kurt D <[hidden email]>
> wrote:
>
> > Problem: Scripts work fine when run on the primary machine, but not
> > when run from remote agents.
> >
> > Background: I'm running a Windows Server (2008R2) with remote agents
> > on RedHat Linux 6 machines. Everything is running JMeter at version
> > 3.1. I've made appropriate and identical Hosts file entries on the
> > Windows box and the Linux boxes, and verified that I can manually
> > browse to my test site in all locations via browser. Linux boxes are
> > running jmeter-server. All machines reside in the same domain.
> >
> Did you check connectivity between servers (jmeter-server <=> jmeter
> client) ?
>
> >
> > Details: I'm using a Results Tree listener for troubleshooting. Pages
> > appear to be working correctly (I'm seeing response code "200" in the
> > Sampler result tabs) BUT - there is nothing displayed in any of the
> > Response Data tabs. As I'm extracting  response data for login
> > operations (e.g. JSESSIONID, VIEWSTATE), I'm never really getting logged
> in.
> >
>
> In distributed mode JMeter since 2.9 strips responses data for scalability.
> If you need those for debugging, just put in user.properties:
>
> mode=Standard
>
> But switch back to default mode for your load test.
>
> >
> > Any thoughts on further troubleshooting would be greatly appreciated.
> >
> > Thanks,
> > Kurt
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>



--
Cordialement.
Philippe Mouawad.
Reply | Threaded
Open this post in threaded view
|

RE: Remote Start

Hohmann, Kurt D
Well, that certainly does answer my question quite nicely - thank you for that! In setting up that tool, I obviously overlooked the key bit about it not working in distributed mode.

As far as my usage, it seemed like the correct tool for this usage - because appending a JSESSION ID to the URL in this application is used in lieu of a cookie to maintain the user session, it seemed tailor made. I'll try using a RegEx Extractor instead and just append the path statements with a variable pulled from that.

Thanks again!
Kurt



-----Original Message-----
From: Philippe Mouawad [mailto:[hidden email]]
Sent: Wednesday, January 25, 2017 12:37 PM
To: JMeter Users List <[hidden email]>
Subject: Re: Remote Start

Hello Kurt,
If you're using HTTP_URL_Re-writing_Modifier, read the Manual :-) :
http://jmeter.apache.org/usermanual/component_reference.html#HTTP_URL_Re-
writing_Modifier

Could you give more details on why you use HTTP URL Re-writing Modifier, by coincidence, I've just sent a proposal on dev mailing list to deprecated (and remove) this element in future version so I'm interested to know how it is used by users.

Here is an excerpt from discussion:

------------------------------------------------------------------------------------------------------------------------
What do you think of deprecating HTML Link Parser and HTTP URL Re-writing Modifier?

   - I am not sure they are widely used
   - Their design does not suit well for performance as :
      - they require Previous Response, as a consequence, they do not work
      in Distributed mode
      - they use a Dom parser + Tidy
      - They are  based on old HTML parser so I don't think they work
   properly with new HTML 5 code
   - They suffer from old bugs:
      - https://bz.apache.org/bugzilla/show_bug.cgi?id=17252
      - https://bz.apache.org/bugzilla/show_bug.cgi?id=59943 => It was not
      reported on this element, but investigation showed it was affected

We could ask question on User mailing list and twitter to see if it's used.
------------------------------------------------------------------------------------------------------------------------


Regards
Philippe


On Wed, Jan 25, 2017 at 6:24 PM, Hohmann, Kurt D <[hidden email]>
wrote:

> Thanks Philippe!
>
> I was not aware of the 'mode=Standard' switch - I had skipped a few
> releases and never picked up on that one when I upgraded to 3.1.
> However, it's not working as I expected it to.
>
> If I have that switch turned on in my user.properties, the script runs
> fine. The user is logged in, the responses look good, and the script
> completes without error.
>
> As soon as I comment it out, the script fails at the point of login.
> I've tried this a few times with the same user data, same simple
> script, same jmeter client. It's as though the response data *has* to
> be reported back to the jmeter server in order for the HTTP URL
> Re-writing Modifier to pick up and apply the JSESSIONID.
>
> It's a workaround to leave that item in place in user-properties, but
> based on what you said about it (and the fact that it's now shut off
> by default), I have concerns about the viability of a larger load test
> if that's in place.
>
> Thanks,
> Kurt
>
>
> -----Original Message-----
> From: Philippe Mouawad [mailto:[hidden email]]
> Sent: Tuesday, January 24, 2017 2:29 PM
> To: JMeter Users List <[hidden email]>
> Subject: Re: Remote Start
>
> On Fri, Jan 20, 2017 at 8:01 PM, Hohmann, Kurt D
> <[hidden email]>
> wrote:
>
> > Problem: Scripts work fine when run on the primary machine, but not
> > when run from remote agents.
> >
> > Background: I'm running a Windows Server (2008R2) with remote agents
> > on RedHat Linux 6 machines. Everything is running JMeter at version
> > 3.1. I've made appropriate and identical Hosts file entries on the
> > Windows box and the Linux boxes, and verified that I can manually
> > browse to my test site in all locations via browser. Linux boxes are
> > running jmeter-server. All machines reside in the same domain.
> >
> Did you check connectivity between servers (jmeter-server <=> jmeter
> client) ?
>
> >
> > Details: I'm using a Results Tree listener for troubleshooting.
> > Pages appear to be working correctly (I'm seeing response code "200"
> > in the Sampler result tabs) BUT - there is nothing displayed in any
> > of the Response Data tabs. As I'm extracting  response data for
> > login operations (e.g. JSESSIONID, VIEWSTATE), I'm never really
> > getting logged
> in.
> >
>
> In distributed mode JMeter since 2.9 strips responses data for scalability.
> If you need those for debugging, just put in user.properties:
>
> mode=Standard
>
> But switch back to default mode for your load test.
>
> >
> > Any thoughts on further troubleshooting would be greatly appreciated.
> >
> > Thanks,
> > Kurt
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>



--
Cordialement.
Philippe Mouawad.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]