Community
Participate
Working Groups
As reported by : 1. Create a new empty workspace and start Eclipse and make sure IAC is enabled in Preferences. 2. Start Profile Configuration and create a new 'External Java Application' instance, select default 'localhost:10002' and click 'Test Connection'. 3. In shell, check 'ps' and verify whether process 'ACServer' is started by Eclipse. Profile an application. The first time I clicked on the "Profile" button, I got the message: 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. org.eclipse.tptp.platform.execution.exceptions.AgentControllerUnavailableException: at org.eclipse.tptp.platform.execution.util.internal.AgentControllerFactory.createConnection(AgentControllerFactory.java:55) at org.eclipse.tptp.platform.execution.util.internal.AgentControllerPool.createConnection(AgentControllerPool.java:190) at org.eclipse.tptp.platform.execution.util.internal.AgentControllerPool.getConnection(AgentControllerPool.java:152) at org.eclipse.tptp.platform.execution.util.internal.AgentControllerPool.getConnection(AgentControllerPool.java:83) at org.eclipse.tptp.platform.jvmti.client.internal.launcher.util.AgentControllerDelegate.getConnection(AgentControllerDelegate.java:47) at org.eclipse.tptp.platform.jvmti.client.internal.launcher.util.AgentControllerDelegate.getConnection(AgentControllerDelegate.java:52) at org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIDelegateHelper.connectToAgentController(TIDelegateHelper.java:395) at org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIDelegateHelper.launch(TIDelegateHelper.java:310) at org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIJavaLauncherDelegate.launch(TIJavaLauncherDelegate.java:37) at org.eclipse.tptp.trace.ui.internal.launcher.core.LauncherUtility.delegateInit(LauncherUtility.java:1163) at org.eclipse.tptp.trace.ui.provisional.launcher.PrimaryLaunchDelegate.run(PrimaryLaunchDelegate.java:195) at java.lang.Thread.run(Thread.java:595) However, checked with ps and noticed that ACServer was actually running... So, I pressed on the profile button a second time and the profiling session did start successfully.
I would add that this problem is, of course, not deterministic, as it is a synchronization problem. If Eclipse is not fast enough to start up the IAC, the first time you try to profile it says it can't find it at the specified port. Maybe increasing the timeout could help, at least when profiling for the first time (i.e.: IAC had not been started before).
This has been fixed by patch to 220197. I tetsed with M5 and M6 build and couldn't reproduce this anymore. *** This bug has been marked as a duplicate of bug 220197 ***
closing