Eclipse Community Forums: Test and Performance Tools Platform (TPTP) » HTTP Recording stops immediately after start-up (FireFox) or never records data (IE)

Home » Archived » Test and Performance Tools Platform (TPTP) » HTTP Recording stops immediately after start-up (FireFox) or never records data (IE)

HTTP Recording stops immediately after start-up (FireFox) or never records data (IE) [message #127053]

Thu, 20 March 2008 06:19

Eclipse User

Originally posted by: mshekov.gmx.de

Hello,

I just installed TPTP using the Update-Manager (Version 4.4.1). I am using a
recent Eclipse Version on Windows XP Pro. I created a servlet-Webapplication
which is deployed on a JBoss application server (I am using the JBossIDE
plugin), it runs on localhost:8080.

I then right-clicked on the project that contains the servlet sources and
created a new "HTTP Recording" test.

However, I am not really able to test this feature. When I started this for
the very first time I had to accept some warnings from the integrated
Windows firewall (I approved all requests, so that no ports should be
blocked). However, the recording stops immediately after it started. This is
the output of the "Recorder control" view:

- Recording started
- Connecting to agent controller on host 'localhost' and port '10002'
- Deploying required recorder files
- Sending commandInit
- Sending commandStartRecording
- Sending commandStartApp Firefox
/* for one second nothing happens */
- Recording completed
- Testgeneration started
....

There are no recorded HTTP requests, as the plugin didn't even try to record
anything. Note that this only happens when using Firefox.

When I then setup TPTP to use InternetExplorer 7 I get another problem. With
IE the Recorder control view behaves properly in a sense that after "Sending
commandStartApp..." it actually waits for input. However, even if I then
visit the Servlet-Page using that IE window that was opened, it won't record
my GET-Requests ("KBytes recorded" stays at 0 all the time).

Ideas ?

Kind regards,
Marius Shekow

Re: HTTP Recording stops immediately after start-up (FireFox) or never records data (IE) [message #127204 is a reply to message #127053]

Fri, 21 March 2008 11:02

Eclipse User

Hi,

On the Firefox issue, I would first check the
Window->Preferences->Test->URL Recorder and verify that the location is
pointing to your FireFox install properly, such as C:\Program
Files\Mozilla Firefox\firefox.exe.

For the IE recording, I would check the settings after the recording
starts. There is a check box on Tools->Internet options->Connections->Lan
Settings labeled "By-pass proxy server for local connections". Local
traffic will not get recorded if this box is checked. Recording traffic
on the local machine is a special case. Try using the network IP address
of the machine instead of using "localhost" to connect to your server. If
problems continue, it may be an easier choice to record from a different
machine rather than directly on the local host machine.

Be aware that if your application opens connections to the server directly
and by-passes the our proxy server recorder, that traffic will not be
recorded.

Hope this helps. Finally, note that I am a bit concerned that something
may be awry in your installation throught whatever sequence of updates
might have been done. If you continue to have issues, a fresh install
might help.

DuWayne

Re: HTTP Recording stops immediately after start-up (FireFox) or never records data (IE) [message #127293 is a reply to message #127204]

Tue, 25 March 2008 12:15

Eclipse User

Originally posted by: mshekov.gmx.de

Hello again,

About the firefox issue: the URL is setup correctly (and also the Firefox
application was started) but the problem remains the same.

I then had a closer look about what the Internet Explorer is doing.
Apparently one cannot tell the Internet Explorer (or better: the Microsoft
Windows Update Tool, as it doesn't serve any other purpose for me) to use a
proxy whatsoever on this machine. I was having a look at the network
activity (I did see that port 1090 was opened by the java-process, listening
for incoming connections). The Internet explorer never connected to it, even
tho I setup every f*cking protocol to use it, hehe. But then I opened also
the Firefox (manually) while keeping the IE open (in order to let the
recorder running). Then I manually setup the same local proxy in Firefox and
tried to open the URL which should be tested. This time it was able to
establish a connection, but I never got any output (TCPView told me the
connection had the status "ESTABLISHED", but that's about it, nothing else
happened). I have no idea why the proxy won't give me the output.

Kind regards,
Marius Shekow

Re: HTTP Recording stops immediately after start-up (FireFox) or never records data (IE) [message #131862 is a reply to message #127053]

Fri, 27 June 2008 11:42

Eclipse User

Sorry for the late reply.

Let's break this up into 3 issues and tackle each one separately:
1. Basic ability to record.
2. Recording the desired application.
3. The Firefox recording problem.

1. Basic ability to record.

Do not modify any of the IE proxy settings. When the recorder starts and
the socks proxy is set, all traffic is routed there. By default, this
will be on port 1080.

Select Internet Explorer for recording. Browse to some outside web site
such as Google or eclipse.org for a couple of pages. See that you get
data recording and a URL Test is generated when you stop the recording.

2. Recording the desired application

There is a known problem in our release notes with Internet Explorer
recording traffic to a server on the local machine. IE knows the
destination is on the local machine, so it bypasses the proxy server.
(Also, make sure the "bypass proxy for local traffic is not checked in the
connection settings).

The work-around for this issue with IE recording is to substitute the host
machine IP address for the destination in your URL, such as
http://xxx.xxx.xxx.xxx/myhomepage.html when recording.

Bear in mind that if your application opens separate socket conversations
between the client and server without being directed to our proxy, that
traffic will not be recorded.

3. For the Firefox problem

I believe the settings have been mangled. Also, not sure what version you
are using. You may want to update to version 3 that was recently
released.

To correct the settings and hopefully get Firefox working with the
recorder, delete *.js under a user settings directory whose path is
something like this:

C:\Documents and Settings\username\Application
Data\Mozilla\Firefox\Profiles\xb81x7th.default

xb81x7th.default is a directory.

After deleting *.js, restart Firefox to initialize settings again. Close
Firefox and retry recording using Firefox.

Hope the above helps solve the problems.

Re: HTTP Recording stops immediately after start-up (FireFox) or never records data (IE) [message #131898 is a reply to message #131862]

Tue, 01 July 2008 06:07

Eclipse User

Originally posted by: manuel.weiss.stud.uni-due.de

Hello,

I have have the same problem when i try to record with Firefox. I have
followed your advice and deleted the *.js files but it is still not
working. Do you have any other suggestions how to solve this problem?

Greetings,
Manuel

> Sorry for the late reply.
>
> Let's break this up into 3 issues and tackle each one separately:
> 1. Basic ability to record.
> 2. Recording the desired application.
> 3. The Firefox recording problem.
>
> 1. Basic ability to record.
>
> Do not modify any of the IE proxy settings. When the recorder starts
> and the socks proxy is set, all traffic is routed there. By default,
> this will be on port 1080.
>
> Select Internet Explorer for recording. Browse to some outside web site
> such as Google or eclipse.org for a couple of pages. See that you get
> data recording and a URL Test is generated when you stop the recording.
>
> 2. Recording the desired application
>
> There is a known problem in our release notes with Internet Explorer
> recording traffic to a server on the local machine. IE knows the
> destination is on the local machine, so it bypasses the proxy server.
> (Also, make sure the "bypass proxy for local traffic is not checked in
> the connection settings).
>
> The work-around for this issue with IE recording is to substitute the
> host machine IP address for the destination in your URL, such as
> http://xxx.xxx.xxx.xxx/myhomepage.html when recording.
>
> Bear in mind that if your application opens separate socket
> conversations between the client and server without being directed to
> our proxy, that traffic will not be recorded.
>
> 3. For the Firefox problem
>
> I believe the settings have been mangled. Also, not sure what version
> you are using. You may want to update to version 3 that was recently
> released.
> To correct the settings and hopefully get Firefox working with the
> recorder, delete *.js under a user settings directory whose path is
> something like this:
>
> C:\Documents and Settings\username\Application
> Data\Mozilla\Firefox\Profiles\xb81x7th.default
>
> xb81x7th.default is a directory.
>
> After deleting *.js, restart Firefox to initialize settings again.
> Close Firefox and retry recording using Firefox.
>
> Hope the above helps solve the problems.
>
>
>

Re: HTTP Recording stops immediately after start-up (FireFox) or never records data (IE) [message #132002 is a reply to message #131898]

Wed, 02 July 2008 07:27

Eclipse User

Hi Manuel,
What are your symptoms? What version of TPTP and Firefox are you using?

Paul
"Manuel Weiss" <manuel.weiss@stud.uni-due.de> wrote in message
news:g4cvkd$pmt$1@build.eclipse.org...
> Hello,
>
> I have have the same problem when i try to record with Firefox. I have
> followed your advice and deleted the *.js files but it is still not
> working. Do you have any other suggestions how to solve this problem?
>
> Greetings,
> Manuel
>
>> Sorry for the late reply.
>>
>> Let's break this up into 3 issues and tackle each one separately:
>> 1. Basic ability to record.
>> 2. Recording the desired application.
>> 3. The Firefox recording problem.
>>
>> 1. Basic ability to record.
>>
>> Do not modify any of the IE proxy settings. When the recorder starts and
>> the socks proxy is set, all traffic is routed there. By default, this
>> will be on port 1080.
>>
>> Select Internet Explorer for recording. Browse to some outside web site
>> such as Google or eclipse.org for a couple of pages. See that you get
>> data recording and a URL Test is generated when you stop the recording.
>>
>> 2. Recording the desired application
>>
>> There is a known problem in our release notes with Internet Explorer
>> recording traffic to a server on the local machine. IE knows the
>> destination is on the local machine, so it bypasses the proxy server.
>> (Also, make sure the "bypass proxy for local traffic is not checked in
>> the connection settings).
>>
>> The work-around for this issue with IE recording is to substitute the
>> host machine IP address for the destination in your URL, such as
>> http://xxx.xxx.xxx.xxx/myhomepage.html when recording.
>>
>> Bear in mind that if your application opens separate socket conversations
>> between the client and server without being directed to our proxy, that
>> traffic will not be recorded.
>>
>> 3. For the Firefox problem
>>
>> I believe the settings have been mangled. Also, not sure what version
>> you are using. You may want to update to version 3 that was recently
>> released.
>> To correct the settings and hopefully get Firefox working with the
>> recorder, delete *.js under a user settings directory whose path is
>> something like this:
>>
>> C:\Documents and Settings\username\Application
>> Data\Mozilla\Firefox\Profiles\xb81x7th.default
>>
>> xb81x7th.default is a directory.
>>
>> After deleting *.js, restart Firefox to initialize settings again. Close
>> Firefox and retry recording using Firefox.
>>
>> Hope the above helps solve the problems.
>>
>>

Previous Topic:	Not all events are recorded by Automated GUI Recorder
Next Topic:	Autonomic Computing \| Help Required

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Apr 25 21:52:58 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter