jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepak Shetty <>
Subject Re: Issue with GWT Application
Date Fri, 28 Aug 2009 21:11:40 GMT
GWT is still an HTTP based AJAX app  , it doesnt need any special document.

You need to compare what your browser sends (using any browser sniffer like
livehttpheaders and FF) with what you send from Jmeter by enabling View
Results tree. Normally needs you to use Post Processors to extract data from
the previous page and post it as part of the next request. Like I said look
through the archives and the wiki on Jmeter ...

If you are getting Session expire as previously posted then you arent
passing the session id correctly ... See how your app manages session id
(typically a cookie , sometimes URL rewriting)

Its because you get Http 200 , Jmeter will report this is as success. You
must tell it when a page is corrected by asserting the response, a test
(jmeter or otherwise) without assertions is pretty much a bad test.


On Fri, Aug 28, 2009 at 2:04 PM, Hari Kishore <>wrote:

> Hi,
>    I am getting response code 200 from server, but the problem is the data
> is not submitted into the database. All the requests are RPC requests. I can
> see different sessionid are assigned for the users for every hit on the
> serve page. I can see this in the server log. Any docment on GWT testing
> with Jmeter is appreciated or links...
> Thanks
> Hari
> -----Original Message-----
> From: Deepak Shetty []
> Sent: Friday, August 28, 2009 1:39 PM
> To: JMeter Users List
> Subject: Re: Issue with GWT Application
> hi
> a. By default JMeter errors are  HTTP errors(5xx or 4xx status codes). You
> must add response assertions based on what your page should have (e.g.
> Success should be displayed, title of the page should be X, there should be
> no error messages etc depending on your app) if you want your app to show
> up
> as errors
> b.  Qts like these been answered multiple times in these forums, please
> search the archives. There is also documentation on what to do when the
> browser works but jmeter doesnt seem to. You might have recorded the
> sessionids when you recorded the script and you are resending the requests
> with the same session id  (or no session id) or you probably arent using an
> HTTPCookie manager.
> regards
> deepak
> On Fri, Aug 28, 2009 at 1:14 PM, Hari Kishore <
> >wrote:
> > Hi All,
> >                    We have a GWT application I recording the script using
> > http proxy. When I replay the script I am not able to submit the data
> into
> > the database after action clicks . But Jmeter runs without any issues.
>  But
> >   if we see the Response header no information is shown or it says
> session
> > expired. Can anybody help me how to work with GWT / AJAX  Load testing
> using
> > Jmeter...
> >
> >
> > Thanks
> > Hari
> >
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message