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 <[email protected]>
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:[email protected]]
> Sent: Tuesday, January 24, 2017 2:29 PM
> To: JMeter Users List <[email protected]>
> Subject: Re: Remote Start
>
> On Fri, Jan 20, 2017 at 8:01 PM, Hohmann, Kurt D <[email protected]>
> 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: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
--
Cordialement.
Philippe Mouawad.
