Re: How to grind a Wicket application

First suggestion would be to trace it in an http debugging proxy (fiddler).  Observe the manual test via the browser, run 1 user and 1 run of your script.  Compare the request that you saw fail with an HTTP 4xx.

A few q's:
- are you performing any data checks on the responses?
- do you know why you are getting a 4xx?
- do you have access to the application server logs?
- Have you confirmed if there are any requests you need to parameterize?  Perhaps you are missing a dynamic header value?

I will have to compare the har tool with the TCP Proxy output.  Perhaps (as others have suggested) the HAR converter Python script is buggy?  Has it been properly tested with Grinder 3.11?  Something to consider.

HTH

> On Sep 22, 2014, at 3:57 PM, Adil qureshi <[email protected]> wrote:
> 
> Just a quick question. .why are you not recording using grinder proxy tool...
> Also there is no difference whether its wickets or struts or any other grinder hits url...underlying technology don't impact grinder...
> 
>> On 22 Sep 2014 19:28, "Rafael Barrera Oro" <[email protected]> wrote:
>> Hello!
>> 
>> My goal is to use The Grinder to stress/load test a fairly big (3000 users aprox) Wicket application. For this i started by recording some basic usage using the chrome devtools and then generating a python file using the har2grinder python script (very basic usage, just navigating to the login screen and logging in to the application).
>> 
>> I've noticed in the agent logs that all the request result in a 400 bad request code, however, the final ammount of errors is zero, so i suspect i am making a basic mistake somewhere. 
>> 
>> Anyway, i wanted to ask you if you had any experience in the subject (with or without exporting the HAR)
>> 
>> PD: This is the the site where i found about the har2grinder script:
>> 
>> http://michal.karzynski.pl/blog/2013/09/28/website-performance-script-for-the-grinder-using-har2grinder/
>> 
>> ------------------------------------------------------------------------------
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> _______________________________________________
>> grinder-use mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/grinder-use
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> grinder-use mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/grinder-use

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk

_______________________________________________
grinder-use mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/grinder-use