[Webtest] problem with the proxy - grinder work

Marc Guillemot Marc Guillemot <mguillemot@yahoo.fr>
Tue, 3 Apr 2007 23:14:03 -0700 (PDT)

Hi Michael,

this is the correct config to tell WebTest/HtmlUnit/commons-httpclient to
use a proxy. Who has http-timeout WebTest or the proxy? Have you tried to
monitor the http trafic?


Michael Habbert wrote:
> Hi Folks,
> I wrote last week about my problems using webtest to record a web-session
> for our load-test with=20
> grinder.
> I wrote to the grinder-mailing-list and got:
> -----------
>  >First, I'll ask the obvious question: Did you modify your web tests to
>  >tell the Apache httpclient library to use the TCPProxy as an HTTP proxy=
> -----------
> So what is my answer? Did I tell the apache httpclient to use the tcpprox=
> as an http-proxy by setting:
> <setproxy proxyhost=3D"${ant.proxyHost}" proxyport=3D"${ant.proxyPort}" /=
> or did I not?
> hopefully this is the reason of my http-timeout after some tests ...
> thanks
> --=20
> Mit freundlichen Gr=C3=BC=C3=9Fen
> ------------------------------------------------------------------------
> Michael Habbert
> Michael Habbert wrote:
>> Recently we came up with a new idea:
>> Why don't we start the proxy while our webtest are running?
>> The idea is:
>> 1. Starting the grinder-proxy.
>> 2. Running our webtests
>> 3. Stopping the proxy.
>> 4. Running the grinder with the webtest-recorded script.py.
>> Well after doing the configuration-changes the recording fails:
>> ------------
>>       [java]      [java] createSimpleWorkflowDef:
>>       [java]      [java] [clickButton] ERROR
>> (com.gargoylesoftware.htmlunit.html.HtmlPage) - Error=20
>> loading javascript from [http://bendera:8888/adds/functions.js]:
>>       [java]      [java] [clickButton]
>> org.apache.commons.httpclient.NoHttpResponseException: The=20
>> server bendera failed to respond
>> --------------
>> So the proxy is still running (using the -console parameter), but no
>> error-log, no recording script ;-/
>> Without the proxy my webtests are running fine without any failure.
>> Starting the proxy befor=20
>> starting the webtest the tests fail after the 12.th test with different
>> not-responding-exceptions=20
>> (different js-files loading). In fact the failing test is not special -
>> one of the prior test is=20
>> doing a similar test and works well.
>> So is there a bug in the Proxy, who can I increase the debug-output of
>> the proxy?
> First, I'll ask the obvious question: Did you modify your web tests to=20
> tell the Apache httpclient library to use the TCPProxy as an HTTP proxy?
> Best (only) debug for the TCPProxy is to run it in echo mode (don't=20
> specify -http). You should see everything it sees. Things to look for:=20
> Do you see an outbound request? Do you see the response coming back from=
> the server? Are connections unexpectedly terminated? Check the server=20
> logs - any complaints there?
> - Phil
> Notice:  This email message, together with any attachments, may contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
> entities,  that may be confidential,  proprietary,  copyrighted  and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this b=
> email and then delete it.

View this message in context: http://www.nabble.com/problem-with-the-proxy-=
Sent from the WebTest mailing list archive at Nabble.com.