If you add a View Results Tree Listener to the Proxy Server, you can
check what is being sent and received by the browser, and compare that
with the test plan.
S
On 22/11/06, Noam Paz <[EMAIL PROTECTED]> wrote:
Hi Tobias,
I would concentrate on parameter extracting. This would *probably* be the
solution; let's try the second possibility (Browser-derived headers) only if
the first one does not work.
You said
>>
I have analysed the responses and also tried to extract the "jsf_tree" and
the jsf_state with help of the regex expression extractor.
<<
My first step would be to validate that you were able to extract their values
correctly.
Please validate it looking at the parameters' values on the "request" tab of a
view result tree.
In your first mail you mentioned
>> "jsf_tree64", "jsf_state64" and a "cid"
can all 3 be extracted from previous replies?
Best regards / Viele Grüße
Noam Paz
"Tobias Knierim" <[EMAIL PROTECTED]>
22.11.2006 16:51
To
"'JMeter Users List'" <jmeter-user@jakarta.apache.org>
cc
Please respond to
"JMeter
Users List" <jmeter-user@jakarta.apache.org>
Subject
AW: AW: Load testing seam applications with jmeter
Hi Noam,
thanks for the suggestions.
I have analysed the responses and also tried to extract the "jsf_tree" and
the jsf_state with help of the regex expression extractor.
The behaviour of the application doesn't change even with Browser-derived
headers active.
Maybe I should give some more information on the app that I was testing and
on the testplan.
The applicaltion is the seam-booking example coming from jboss and you can
watch it here: http://seam.demo.jboss.com/home.seam
I've just installed it at a local jboss.
The test should be able to login, search and book a hotel, cancel the
booking and just lock out after all is done.
I also want to insert a csv dataset, using it to login some different users.
If you're interested in my testplan, maybe I can up the jmx file to let you
have a closer look at it.
-----Ursprüngliche Nachricht-----
Von: Noam Paz [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 22. November 2006 16:16
An: JMeter Users List
Betreff: Re: AW: Load testing seam applications with jmeter
Tobias,
I have 2 suggestion for you:
- analyse the responses you get. Maybe you have to extract those parameters
and send them on following requests.
- maybe (not very probable) you have to use a Browser-derived headers. When
recording, mark this option checked.
Hope that helps
Best regards / Viele Grüße
Noam Paz
"Tobias Knierim" <[EMAIL PROTECTED]>
22.11.2006 16:09
To
"'JMeter Users List'" <jmeter-user@jakarta.apache.org>
cc
Please respond to
"JMeter Users List" <jmeter-user@jakarta.apache.org>
Subject
AW: Load testing seam applications with jmeter
Sure I did, but this doesn't work either.
-----Ursprüngliche Nachricht-----
Von: sebb [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 22. November 2006 16:06
An: JMeter Users List
Betreff: Re: Load testing seam applications with jmeter
Did you add a Cookie Manager to the test plan?
On 22/11/06, Tobias Knierim <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I'm trying to load test a seam application with client site state saving.
I
> tried to record a test using both, the proxy server and badboy. Neither of
> them got me a running testplan. After looking over the testplan I realised
> the parameters "jsf_tree64", "jsf_state64" and a "cid" (conversation id).
>
> Just have tried anything I could think of to get this test running, but
> without success.
>
> Any help to load test this app would be great
>
> Best regards
>
> Tobias Knierim
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is strictly
forbidden.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
