Hi Koen,
The bootstrap and User Agent worked for JMeter!!
Now from JMeter I am able to do operations on database thru Wt
But I am not fully satisfied as you know.
Its not same as Wt accessed from a browser. Is it because of JavaScript?
On Mon, Jun 11, 2012 at 6:27 PM, Koen Deforche <[email protected]> wrote:
> Hey Mohammed,
>
> 2012/6/11 Mohammed Rashad <[email protected]>:
> > Is there any way?
> >
> > What about siege[1]?
> >
> > [1] http://www.joedog.org/siege-home/
> >
> > When I tried sending request using JMeter i can see request coming in Wt
> app
> > log but work is not getting done (eg: a db insertion)
>
> Ah. That's because JMeter is not making the redirect which is returned
> in the first reply. You can avoid this problem by enabling progressive
> bootstrap (which you'll only want for this testing anyway), or by
> including the JMeter user-agent string in the bot list (both settings
> in your wt_config.xml).
>
> JMeter or another similar tool is probably the way forward, unless you
> go for one of the online test services I mentioned in my previous
> mail.
>
> > but when I tested using WTestEnvironment linking libwttest.so its
> creating a
> > sesssion inserting data and destroying session
>
> A WTestEnvironment is not that bad actually, but it bypasses many
> things in Wt, so if you need prove that Wt is not the limiting factor,
> it is not suitable. It also by-passes the thread pool which may be a
> limiting factor if the application is I/O bound.
>
> > Can you make it clear why we cant mae/simulate AJAX request or a browser?
> > There will be some way Web Browser communicates with Wt. I think If I
> know
> > the underlying mechanism then i can do ?
>
> Wt not only generates unique ID's for all form elements and 'signals'
> every time, it also generates unique session IDs and page IDs that are
> kept in constants somewhere deep inside JavaScript, which are all
> needed for a browser to create valid requests. Part of this is
> consequential of how Wt takes charge of many aspects of web
> development, but also intentional to make it hard to DoS a wt
> application, and we've even added more features (disabled by default)
> in 3.2.1 such as an "Ajax puzzle" to thwart bots that are mounting a
> DoS attack.
>
> You can easily see the kind of requests the browser creates, using
> tools like Chrome Inspector or Firebug, and by looking at the contents
> of the Ajax request headers.
>
> Regards,
> koen
>
--
Regards,
Rashad
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
