Eclipse Community Forums: Test and Performance Tools Platform (TPTP)

Home » Archived » Test and Performance Tools Platform (TPTP) » TPTP URL test recording problems

TPTP URL test recording problems [message #100213]

Tue, 05 June 2007 11:46

Eclipse User

Hi all

I have 2 issues:

1) I am using TPTP 4.2.1 and IE 7 to record a performance test on a web
application. The application is hosted on a separate machine and includes
an IFrame populated from another remote server and also numerous AJAX
requests.

It records the tests fine and i can generate the Test code to be run.

However, whenever i run the test the progress bar gets to 93% and then
hangs. Even if i leave it for 1 hour it does not complete (the test only
involves about 10 requests and the number of iterations and users are both
set to 1!). I then stop the test from the progress panel and it appears to
stop. However the java process for the test continues to run and consumes
50% of my machines CPU).

Is there anything i need to configure to ensure this works?

I have even tried creating a really simple test which accesses google and
i get exactly the same problem so i am presuming it is a
setup/configration thing...

2) How can i get the test recorder to record information sent on different
port from port 80? Whenever i record a test against a local app
deployment on port 8081 nothing gets recorded?

many thanks people

Will

Re: TPTP URL test recording problems [message #100440 is a reply to message #100213]

Wed, 06 June 2007 10:00

Eclipse User

I have found an error in my eclipse log:

!ENTRY org.eclipse.hyades.test.core 1 0 2007-06-05 14:55:33.678
!MESSAGE org.eclipse.hyades.execution.invocation.RemoteInvocationExce ption
!STACK 0
org.eclipse.hyades.execution.invocation.RemoteInvocationExce ption
at
org.eclipse.hyades.execution.local.SessionImpl.invokeRemote( SessionImpl.java:107)
at
org.eclipse.hyades.execution.local.RemoteObjectStub.delegate RemoteCall(RemoteObjectStub.java:87)
at
org.eclipse.hyades.execution.local.ExecutorStub.kill(Executo rStub.java:92)
at
org.eclipse.hyades.execution.local.ExecutorStub.kill(Executo rStub.java:104)
at
org.eclipse.hyades.execution.harness.TestExecutionHarness.st opTest(TestExecutionHarness.java:2575)
at
org.eclipse.hyades.execution.harness.TestExecutionHarness.st opTest(TestExecutionHarness.java:2595)
at
org.eclipse.hyades.test.core.internal.launch.processes.TestE xecutionProcess.terminate(TestExecutionProcess.java:138)
at org.eclipse.debug.core.Launch.terminate(Launch.java:229)
at
org.eclipse.debug.internal.core.LaunchManager.shutdown(Launc hManager.java:1961)
at org.eclipse.debug.core.DebugPlugin.stop(DebugPlugin.java:560 )
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$3 .run(BundleContextImpl.java:1032)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:1028)
at
org.eclipse.osgi.framework.internal.core.BundleHost.stopWork er(BundleHost.java:396)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.stop (AbstractBundle.java:400)
at
org.eclipse.core.runtime.internal.adaptor.BundleStopper.basi cStopBundles(BundleStopper.java:86)
at
org.eclipse.core.runtime.internal.adaptor.BundleStopper.stop Bundles(BundleStopper.java:73)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAdaptorHook .frameworkStopping(EclipseAdaptorHook.java:156)
at
org.eclipse.osgi.baseadaptor.BaseAdaptor.frameworkStopping(B aseAdaptor.java:288)
at
org.eclipse.osgi.framework.internal.core.Framework.shutdown( Framework.java:529)
at
org.eclipse.osgi.framework.internal.core.Framework.close(Fra mework.java:440)
at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.jav a:41)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(Ecl ipseStarter.java:423)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
Caused by:
org.eclipse.hyades.internal.execution.local.control.Inactive AgentException
at
org.eclipse.hyades.internal.execution.local.control.AgentImp l.invokeCustomCommand(AgentImpl.java:480)
at
org.eclipse.hyades.execution.local.SessionImpl.invokeRemote( SessionImpl.java:104)
... 31 moreI have found an error in my eclipse log:

!ENTRY org.eclipse.hyades.test.core 1 0 2007-06-05 14:55:33.678
!MESSAGE org.eclipse.hyades.execution.invocation.RemoteInvocationExce ption
!STACK 0
org.eclipse.hyades.execution.invocation.RemoteInvocationExce ption
at
org.eclipse.hyades.execution.local.SessionImpl.invokeRemote( SessionImpl.java:107)
at
org.eclipse.hyades.execution.local.RemoteObjectStub.delegate RemoteCall(RemoteObjectStub.java:87)
at
org.eclipse.hyades.execution.local.ExecutorStub.kill(Executo rStub.java:92)
at
org.eclipse.hyades.execution.local.ExecutorStub.kill(Executo rStub.java:104)
at
org.eclipse.hyades.execution.harness.TestExecutionHarness.st opTest(TestExecutionHarness.java:2575)
at
org.eclipse.hyades.execution.harness.TestExecutionHarness.st opTest(TestExecutionHarness.java:2595)
at
org.eclipse.hyades.test.core.internal.launch.processes.TestE xecutionProcess.terminate(TestExecutionProcess.java:138)
at org.eclipse.debug.core.Launch.terminate(Launch.java:229)
at
org.eclipse.debug.internal.core.LaunchManager.shutdown(Launc hManager.java:1961)
at org.eclipse.debug.core.DebugPlugin.stop(DebugPlugin.java:560 )
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$3 .run(BundleContextImpl.java:1032)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:1028)
at
org.eclipse.osgi.framework.internal.core.BundleHost.stopWork er(BundleHost.java:396)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.stop (AbstractBundle.java:400)
at
org.eclipse.core.runtime.internal.adaptor.BundleStopper.basi cStopBundles(BundleStopper.java:86)
at
org.eclipse.core.runtime.internal.adaptor.BundleStopper.stop Bundles(BundleStopper.java:73)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAdaptorHook .frameworkStopping(EclipseAdaptorHook.java:156)
at
org.eclipse.osgi.baseadaptor.BaseAdaptor.frameworkStopping(B aseAdaptor.java:288)
at
org.eclipse.osgi.framework.internal.core.Framework.shutdown( Framework.java:529)
at
org.eclipse.osgi.framework.internal.core.Framework.close(Fra mework.java:440)
at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.jav a:41)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(Ecl ipseStarter.java:423)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
Caused by:
org.eclipse.hyades.internal.execution.local.control.Inactive AgentException
at
org.eclipse.hyades.internal.execution.local.control.AgentImp l.invokeCustomCommand(AgentImpl.java:480)
at
org.eclipse.hyades.execution.local.SessionImpl.invokeRemote( SessionImpl.java:104)
... 31 more

Re: TPTP URL test recording problems [message #100510 is a reply to message #100440]

Wed, 06 June 2007 16:11

Eclipse User

Hi,

There was a defect that was fixed in TPTP 4.3.1 specifically related to
test execution hangs in URL tests that looks like what you are
experiencing. The problem was improper handling of chunk-encoded server
response data. It happens that google a site whose servers respond with
chunk-encoding. The situation seems to be that chunk encoding is becoming
more wide-spread as time goes on. As a result, I would suggest that you
would benefit by switching to TPTP version 4.3.1 or later. The exceptions
you noted are related to this problem.

I am not quite certain what you are doing with port 8081. It seems
implied that you are not using the browser but instead using an
application of some kind to connect to a server on that port. What you
must do in that case to get a recording is to configure the application to
use a proxy and set the proxy port to the default port 1080. If that port
is not available when the recording is started, there will be a message
indicating what port the recorder is listening on that is posted in the
the Window->Show View->Other->Test-Recorder Control.

Hope this helps.
DuWayne

Previous Topic:	TPTP Eclipse plugin
Next Topic:	TPTP4.3.1 release build(TPTP-4.3.1-200702221346) can't profing websphere6.0

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jul 07 17:00:37 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter