Eclipse Community Forums: Test and Performance Tools Platform (TPTP) » Unable to profile application "Read timed out" response from Agent Controller

Home » Archived » Test and Performance Tools Platform (TPTP) » Unable to profile application "Read timed out" response from Agent Controller

Unable to profile application "Read timed out" response from Agent Controller [message #140302]

Thu, 12 February 2009 06:47

Eclipse User

Originally posted by: chwalker.uk.ibm.com

Hi

I'm very new to using TPTP but have been struggling with the following
configuration. My setup is:

- Eclipse Platform 3.4.1 running on WinXP
- TPTP Plugin version 4.5.1
- Java 1.5
- Remote Agent Controller 4.3.0 running on z/OS (latest version of a
z/OS controller)

I have been able to successfully deploy and profile a simple HelloWorld
Java application under this setup but anything more complex seems fail
with the following error:

<snip>
Agent Controller is unavailable under port 10002. Make sure that the
service is started and the port number is correct under preferences.

org.eclipse.core.runtime.CoreException: Agent Controller is unavailable
under port 10002. Make sure that the service is started and the port
number is correct under preferences.
at
org.eclipse.tptp.trace.ui.internal.launcher.core.LauncherUti lity.createCoreException(LauncherUtility.java:124)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.connectToAgentController(TIDelegateHelper.java :415)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.launch(TIDelegateHelper.java:322)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIJ avaLauncherDelegate.launch(TIJavaLauncherDelegate.java:37)
at
org.eclipse.tptp.trace.ui.internal.launcher.core.LauncherUti lity.delegateInit(LauncherUtility.java:1164)
at
org.eclipse.tptp.trace.ui.provisional.launcher.PrimaryLaunch Delegate.run(PrimaryLaunchDelegate.java:195)
at java.lang.Thread.run(Unknown Source)
Caused by:
org.eclipse.tptp.platform.execution.exceptions.AgentControll erUnavailableException:
Error: Unable to connect to the Agent Controller.Read timed out
at
org.eclipse.tptp.platform.execution.client.core.internal.Nod eImpl.connect(NodeImpl.java:128)
at
org.eclipse.tptp.platform.execution.util.internal.AgentContr ollerFactory$EstablishConnection.run(AgentControllerFactory. java:126)
... 1 more
</snip>

The principal error message (the Agent Controller is unavailable under
port 10002) is untrue as I know a connection is made and accepted from
the Agent Controller log (servicelog.log) and that the HelloWorld test
seemed to work. The key error seemes to be the "Read timed out" implying
a missing response back from the controller?

My guess therefore is that either there is some kind of incompatibility
between the Agent Controller or I have incorrectly configured my
application in the Profile Configurations. Potentially the classpath but
this is a simple app with 2 Jar's needed on the classpath only.

Has anyone hit this problem before or have tips to overcome it?

Regards
Chris

Re: Unable to profile application "Read timed out" response from Agent Controller [message #140347 is a reply to message #140302]

Thu, 12 February 2009 12:31

Eclipse User

Hi Chris,

Please attempt using Java 1.4.2 on the agent controller. My guess is that
the workbench is seeing Java 1.5.0 on your Z/OS agent controller, and
therefore defaulting to using an unsupported Java profiler (the Java 1.5+
JVMTI profiler) which is unavailable for Z/OS.

Let me know what happens...

Re: Unable to profile application "Read timed out" response from Agent Controller [message #140369 is a reply to message #140347]

Mon, 16 February 2009 11:30

Eclipse User

Originally posted by: chwalker.uk.ibm.com

Hi Jonathan,

Thanks for the tip. I'm in the process of running the test however, the
remote application I wish to profile pre-req's Java 5.0. Unless this
could be worked around then I fear this could be a real blocker to any
progress.

Regards

Re: Unable to profile application "Read timed out" response from Agent Controller [message #140478 is a reply to message #140369]

Wed, 18 February 2009 18:28

Eclipse User

Hi Chris,

Unfortunately you need to setup the Agent Controller with JVM 1.4 to enabled
JVMPI profiler to work. However, you can try work around the problem by
launching your application as a standalone launch outside of workbench on
the target system:

On the remote system:
- start the Agent Controller
- make sure the AgentController/bin libraries are in the PATH
- launch your application with java -XrunpiAgent:server=controlled
yourApplication.
On the workbench side:
- create an Attach to Java launch configuration and select the target host
and the process launched for attach.

HTH
Eugene.

"Chris Walker" <chwalker@uk.ibm.com> wrote in message
news:gnc4al$4vm$1@build.eclipse.org...
> Hi Jonathan,
>
> Thanks for the tip. I'm in the process of running the test however, the
> remote application I wish to profile pre-req's Java 5.0. Unless this could
> be worked around then I fear this could be a real blocker to any progress.
>
> Regards

Previous Topic:	NullpointerException WorkbenchExecutionDeploymentAdapter.java:502
Next Topic:	NPE in AutomationClientAdapter

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jun 07 09:02:14 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter