Eclipse Community Forums: Test and Performance Tools Platform (TPTP) » on WindXP, profiler hangs at "Connecting to JVMTI agent"

Home » Archived » Test and Performance Tools Platform (TPTP) » on WindXP, profiler hangs at "Connecting to JVMTI agent"

on WindXP, profiler hangs at "Connecting to JVMTI agent" [message #140892]

Tue, 03 March 2009 14:33

Eclipse User

I'm having an problem where the profiler hangs when starting an app at the
"Connecting to JVMTI" agent step.

This is *not* the same as a problem reported in Nov 2008:

http://dev.eclipse.org/newslists/news.eclipse.tptp/msg06835. html
https://bugs.eclipse.org/bugs/show_bug.cgi?id=240677

which manifested itself in the same way. That was caused by the
agentcontroller being compiled with an old version of libstdc++, which is
missing on the target system. That was Ubuntu, this is WinXP.

The interesting thing is the class I want to profile is in an app which
links in more than 50 jar files. If I pull this class out into a new
project with *no* additional jar files required, the profiler starts up
fine.

It appears to be some sort of a race condition or a timeout perhaps caused
by the high overhead of loading/processing all the jar files when my
target class has all those jar files in its classpath.

Running eclipse -debug, I see that the socket it's (apparently) trying to
communicate with is closed. Stack trace below. Could it be that it takes
so long to load/process all those jars that the connection times out?

Thanks,
Jon

Starting application: 735
Application Started: 13203
java.net.SocketException: Socket is closed
at java.net.Socket.getOutputStream(Socket.java:799)
at
org.eclipse.tptp.platform.execution.client.core.internal.Con nectionIm
pl.sendMessage(ConnectionImpl.java:517)
at
org.eclipse.tptp.platform.execution.client.core.internal.Age ntControl
ler.sendCommand(AgentController.java:1203)
at
org.eclipse.tptp.platform.execution.client.agent.internal.Ag entImpl.s
endCommand(AgentImpl.java:353)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper.sendOptions(TIDelegateHelper.java:1083)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper.attachToAgent(TIDelegateHelper.java:751)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper.attachToAgent(TIDelegateHelper.java:675)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper.access$7(TIDelegateHelper.java:673)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper$2.processLaunched(TIDelegateHelper.java:514)
at
org.eclipse.tptp.platform.execution.client.core.internal.Pro cessImpl.
launchAC(ProcessImpl.java:701)
at
org.eclipse.tptp.platform.execution.client.core.internal.Pro cessImpl.
launch(ProcessImpl.java:130)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper.launchProcess(TIDelegateHelper.java:549)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper.launch(TIDelegateHelper.java:347)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIJ avaLaunch
erDelegate.launch(TIJavaLauncherDelegate.java:37)
at
org.eclipse.tptp.trace.ui.internal.launcher.core.LauncherUti lity.dele
gateInit(LauncherUtility.java:1164)
at
org.eclipse.tptp.trace.ui.provisional.launcher.PrimaryLaunch Delegate.
run(PrimaryLaunchDelegate.java:195)
at java.lang.Thread.run(Thread.java:595)
java.net.SocketException: Socket is closed
at java.net.Socket.getOutputStream(Socket.java:799)
at
org.eclipse.tptp.platform.execution.client.core.internal.Con nectionIm
pl.sendMessage(ConnectionImpl.java:517)
at
org.eclipse.tptp.platform.execution.client.core.internal.Age ntControl
ler.sendCommand(AgentController.java:1203)
at
org.eclipse.tptp.platform.execution.client.agent.internal.Ag entImpl.s
endCommand(AgentImpl.java:353)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper$PeriodicPoll.run(TIDelegateHelper.java:1782)
java.net.SocketException: Socket is closed
at java.net.Socket.getOutputStream(Socket.java:799)
at
org.eclipse.tptp.platform.execution.client.core.internal.Con nectionIm
pl.sendMessage(ConnectionImpl.java:517)
at
org.eclipse.tptp.platform.execution.client.core.internal.Age ntControl
ler.sendCommand(AgentController.java:1203)
at
org.eclipse.tptp.platform.execution.client.agent.internal.Ag entImpl.s
endCommand(AgentImpl.java:353)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper.configureDataProcessor(TIDelegateHelper.java:841)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper.attachToAgent(TIDelegateHelper.java:760)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper.attachToAgent(TIDelegateHelper.java:675)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper.access$7(TIDelegateHelper.java:673)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper$2.processLaunched(TIDelegateHelper.java:514)
at
org.eclipse.tptp.platform.execution.client.core.internal.Pro cessImpl.
launchAC(ProcessImpl.java:701)
at
org.eclipse.tptp.platform.execution.client.core.internal.Pro cessImpl.
launch(ProcessImpl.java:130)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper.launchProcess(TIDelegateHelper.java:549)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper.launch(TIDelegateHelper.java:347)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIJ avaLaunch
erDelegate.launch(TIJavaLauncherDelegate.java:37)
at
org.eclipse.tptp.trace.ui.internal.launcher.core.LauncherUti lity.dele
gateInit(LauncherUtility.java:1164)
at
org.eclipse.tptp.trace.ui.provisional.launcher.PrimaryLaunch Delegate.
run(PrimaryLaunchDelegate.java:195)
at java.lang.Thread.run(Thread.java:595)
java.net.SocketException: Socket is closed
at java.net.Socket.getOutputStream(Socket.java:799)
at
org.eclipse.tptp.platform.execution.client.core.internal.Con nectionIm
pl.sendMessage(ConnectionImpl.java:517)
at
org.eclipse.tptp.platform.execution.client.core.internal.Age ntControl
ler.sendCommand(AgentController.java:1203)
at
org.eclipse.tptp.platform.execution.client.agent.internal.Ag entImpl.s
endCommand(AgentImpl.java:353)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHe
lper$PeriodicPoll.run(TIDelegateHelper.java:1782)

Re: on WindXP, profiler hangs at "Connecting to JVMTI agent" [message #140903 is a reply to message #140892]

Tue, 03 March 2009 14:58

Eclipse User

I should have mentioned versions...

Eclipse SDK
Version: 3.4.0
Build id: I20080617-2000

TPTP: 4.5.2

BTW, is it normal that I see multiple versions of then TPTP plugins
under Help->Software updates->Installed software?

Re: on WindXP, profiler hangs at "Connecting to JVMTI agent" [message #141180 is a reply to message #140903]

Wed, 11 March 2009 08:55

Eclipse User

This is a multipart message in MIME format.
--=_alternative 0047055D85257576_=
Content-Type: text/plain; charset="US-ASCII"

Hi Jon,

Are there any errors reported or details you can provide from your Agent
Controller/config/serviclog.log file? Does the class depend on or use any
of the additional jars that are required on the classpath when it worked
so that you had a smaller subset of dependencies? I will try to reproduce
the problem.

It is normal to have multiple versions of TPTP with different names under
Help->Software Updates->Installed Software as these are the different
sub-projects of TPTP. If there are different versions with the same name,
this usually indicates an upgrade from a previous version of TPTP.
--=_alternative 0047055D85257576_=
Content-Type: text/html; charset="US-ASCII"

Hi Jon,
 
 Are there any errors reported or details
you can provide from your Agent Controller/config/serviclog.log file? Does
the class depend on or use any of the additional jars that are required
on the classpath when it worked so that you had a smaller subset of dependencies?
I will try to reproduce the problem.
 
 It is normal to have multiple versions
of TPTP with different names under Help->Software Updates->Installed
Software as these are the different sub-projects of TPTP. If there are
different versions with the same name, this usually indicates an upgrade
from a previous version of TPTP.
--=_alternative 0047055D85257576_=--

Re: on WindXP, profiler hangs at "Connecting to JVMTI agent" [message #141201 is a reply to message #141180]

Wed, 11 March 2009 11:51

Eclipse User

This is a multipart message in MIME format.
--=_alternative 0057278885257576_=
Content-Type: text/plain; charset="US-ASCII"

Hi Jon,

A few further follow-up questions:
Are you running behind a firewall? Have you tried on another machine?

I tried profiling a TPTP ui plug-in and results were returned. Can you
provide an example to reproduce the problem.
--=_alternative 0057278885257576_=
Content-Type: text/html; charset="US-ASCII"

Hi Jon,
 
 A few further follow-up questions:
 Are you running behind a firewall? Have
you tried on another machine?
 
 I tried profiling a TPTP ui plug-in
and results were returned. Can you provide an example to reproduce the
problem.
--=_alternative 0057278885257576_=--

Re: on WindXP, profiler hangs at "Connecting to JVMTI agent" [message #141211 is a reply to message #141201]

Wed, 11 March 2009 15:58

Eclipse User

The extra jar files are not required for operation of the class.

Unfortunately, I can't provide a simple test case for this, as the app is
proprietary. Presumably, one would be able to reproduce the problem by
including many extraneous jar files in the classpath of an app.

Previous Topic:	Other Java code reviews?
Next Topic:	Code coverage?

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 22 20:20:37 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter