Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Test and Performance Tools Platform (TPTP) » Major issues with Eclipse 3.3 and TPTP 4.4
Major issues with Eclipse 3.3 and TPTP 4.4 [message #102419] Tue, 03 July 2007 00:11 Go to next message
Tom Funk is currently offline Tom FunkFriend
Messages: 22
Registered: July 2009
Junior Member
I've exhausted Google and this newsgroup and haven't been able
to get Eclipse 3.3 and TPTP 4.4 working with the IAC.

I think the problem is that I no longer have a DefaultMonitor -- and I
don't know how to recreate one.

After upgrading from E3.2.1/T4.2, thinking that I was getting conflicts
between TPTP 4.2 & 4.4, I removed the previous ProfileProject, along with
the DefaultMonitor and the file system contents.

If this is the root problem, and if someone can point me to how to create
a new DefaultMonitor, we might be able to move on. However, fwiw, even with
a DefaultMonitor in place under E3.2.1/T4.2 I was never able to get
profiling working.

In the interest of completeness, what follows is a laundry list of
TPTP settings and symptoms. I hope I've included everything someone might
need to be able to lend an assist.

In the Profile Execution Environment settings dialog, on the "Monitor" tab,
with "Java Profiling - JRE 1.5 or Newer" selected, clicking "Check
Availability" throws an error dialog:

"An unexpected error occurred while attempting to
establish a connection."

Both the Reason and Details are empty.

When I attempt to profile the app (which executes correctly under both Run
and Debug environments), I get the following error dialog:

"One of the selected launch delegates has failed."

Reason is empty; details contains this:

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.

java.lang.NullPointerException
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.hasProcessTerminated(AutoStartStop.java:275 )
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:113)
at org.eclipse.tptp.platform.execution.client.core.internal.Nod eImpl.connect(NodeImpl.java:117)
at org.eclipse.tptp.platform.jvmti.client.internal.launcher.uti l.AgentControllerDelegate$1$EstablishConnection.run(AgentCon trollerDelegate.java:155)
at java.lang.Thread.run(Thread.java:595)

Under Preferences > Agent Controller, the Integrated Controller is enabled.
The selected JRE matches Eclipse's. To the list of "Machines that should
be given access to IAC," I've added the loopback IP, the real IP, the
hostname and "localhost." IAC Security is off.

Under Preferences > Profiling and Logging, I've changed the Default
Profiling Project name from the default of "ProfileProject" to
"ProfilingProject" (hoping to avoid a name clash w/the 4.2 config). AC
local port is 10002. Under "Application Context," "Java," "JVTMI profier
context provider" and "Basic Java open source action provider" are all
selected.

I've just upgraded to Europa and installed TPTP via the Eclipse update
manager from the Europa Discovery site. I'm using the same project
workspace as before, running Kubuntu 7.04 and Sun Java 1.5.0_11. After
installing TPTP, I restarted Eclipse with the -clean argument.

No errors are being written to ~/.eclipse/.log or to the workspace
..metadata directory.

netstat shows that port 10002 is not in use (but it shouldn't be since I
never downloaded the standalone AC).

Does this cover everything?

Any help on this would be *greatly* appreciated.

Thanks so much.

-=< tom >=-
Tom Funk
Germantown, MD.
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102461 is a reply to message #102419] Tue, 03 July 2007 05:10 Go to previous messageGo to next message
Igor Alelekov is currently offline Igor AlelekovFriend
Messages: 139
Registered: July 2009
Senior Member
Hi Tom,
Try to install Eclipse 3.3 and TPTP 4.4 from download page, not via update
site.
Regards,
Igor
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102513 is a reply to message #102461] Tue, 03 July 2007 12:07 Go to previous messageGo to next message
Joe Toomey is currently offline Joe ToomeyFriend
Messages: 79
Registered: July 2009
Member
Installing via the update site should work equally well as installing
from the zip files on the download page. However, note that all of
Europa is designed to be run from a clean eclipse install (not upgraded
from Callisto or older eclipse bits.) See the following post from Bjorn
Freeman-Benson at eclipse (from the cross-project-issues-dev@eclipse.org
mailing list):

> That's because we did not design for updating from Callisto to
> Europa - you need to start with one of the pre-built Europa distros
> (to be available on Europa-day, June 29th) or start from a new
> Eclipse Platform 3.3 run-time and then install the Europa features
> that you are interested in.
>
> - Bjorn

From your post, I infer that you updated an existing Eclipse install
rather than installing a new Europa eclipse, but I can't be certain of
that. Of all the testing we did in the TPTP project for the Europa
release (and believe me, there was a lot of it:
http://www.eclipse.org/tptp/test/reports/4.4_i4/index.html
http://www.eclipse.org/tptp/test/reports/4.4_i3/index.html
http://www.eclipse.org/tptp/test/reports/4.4_i2/index.html
http://www.eclipse.org/tptp/test/reports/4.4_i1/index.html ), exactly
none of it was done using upgraded installs from Callisto or previous
release.

I'm sorry for the problems you are having with TPTP. The scenarios you
describe should work out of the box, and in our testing scenarios, they
do. We will do whatever we can to help you get unblocked. For the
first step, please start with a clean install (downloading a Europa
package from eclipse.org and then installing TPTP -- using the update
manager should work fine.) I also (always) suggest that when you
install a new major version of eclipse, you start with a new workspace.
You can import any existing projects into that new workspace (you lose
no data), but the workspace also contains metadata from the old eclipse
plugins that may not be applicable for your new eclipse install.

If your symptoms persist, please write back and provide us with the
details. We'll work with you to reproduce the issue and get a resolution.

Thanks for your interest in TPTP.
--Joe
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102557 is a reply to message #102461] Tue, 03 July 2007 12:41 Go to previous messageGo to next message
Tom Funk is currently offline Tom FunkFriend
Messages: 22
Registered: July 2009
Junior Member
Hello, Igor,

Thank you for your response.

> Try to install Eclipse 3.3 and TPTP 4.4 from download page,
> not via update site.

I downloaded the TPTP 4.4 All-in-one package for Linux.

Installed it into a new directory and ran it with -clean using the same
workspace as before.

In the Execution / Profile Configuration Window, Eclipse pauses
while trying to populate the monitor tab. After filling in the
entries for Agent Discoverer, Java Profiling, etc, the following shows up
in the ~/.metadata/.log file:

!SESSION 2007-07-03 08:13:03.520 -----------------------------------------------
eclipse.buildId=I20070625-1500
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86 -clean -data /home/tfunk/Projects/java/Trunk_WS

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 08:13:35.098
!MESSAGE [startIAC: Error Stream] RAServer generated the following output:
[: 46: ==: unexpected operator

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 08:13:35.111
!MESSAGE [startIAC: Error Stream] RAServer generated the following output:
ACServer: error while loading shared libraries: libtptpUtils.so.4:
cannot open shared object file: No such file or directory

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 08:13:37.197
!MESSAGE [startIAC: Output Stream] RAServer generated the following
output: ACServer failed to start.

A find for 'libtptpUtils*' shows the file in the following location:

..../eclipse_3.3/plugins/
org.eclipse.tptp.platform.ac.linux_ia32_4.4.0.v200706020100/
agent_controller/lib/libtptpUtils.so.4.4.0

(there's also a 64-bit version, but I'm running a 32-bit OS).

Clicking Test for Availablity pauses (where it didn't before) and gives
the same error dialog:

"An unexpected error occurred while attempting to establish a connection"

However, the reason and details are still blank. No new information is sent
to the .log file.

I looks like the runtime is expecting to find libtptpUtils.so.4 rather
than libtptpUtils.so.4.4.0. I created a symlink (libtptpUtils.so.4 ==>
libtptpUtils.so.4.4.0) in the same lib directory and reran Eclipse.

The .log file now shows that libtptpLogUtils.so.4 is missing.
libtptpUtils.so.4 was found. symlinking this file (libtptpLogUtils.so.4
==> libtptpLogUtils.so.4.4.0) resolves this error and results in
libtptpConfig.so.4 being missing.

Is there a configuration file in Eclipse somewhere that defines what
versions of native libraries are to be loaded? Could that file be
incorrectly configured?

I could symlink all the libraries, but surely there's a better way to fix
this....?

Thank you for the assist.

-=< tom >=-
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102572 is a reply to message #102557] Tue, 03 July 2007 13:25 Go to previous messageGo to next message
Joe Toomey is currently offline Joe ToomeyFriend
Messages: 79
Registered: July 2009
Member
Tom,

Did you unzip the AC download on a different machine and then copy the
bits to your Linux box? If you unzip the install using "unzip" on the
Linux box, the symlinks are created automatically.

Hope this helps,
--Joe

Tom Funk wrote:
> Hello, Igor,
>
> Thank you for your response.
>
>> Try to install Eclipse 3.3 and TPTP 4.4 from download page,
>> not via update site.
>
> I downloaded the TPTP 4.4 All-in-one package for Linux.
>
> Installed it into a new directory and ran it with -clean using the same
> workspace as before.
>
> In the Execution / Profile Configuration Window, Eclipse pauses
> while trying to populate the monitor tab. After filling in the
> entries for Agent Discoverer, Java Profiling, etc, the following shows up
> in the ~/.metadata/.log file:
>
> !SESSION 2007-07-03 08:13:03.520 -----------------------------------------------
> eclipse.buildId=I20070625-1500
> java.version=1.5.0_11
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
> Command-line arguments: -os linux -ws gtk -arch x86 -clean -data /home/tfunk/Projects/java/Trunk_WS
>
> !ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 08:13:35.098
> !MESSAGE [startIAC: Error Stream] RAServer generated the following output:
> [: 46: ==: unexpected operator
>
> !ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 08:13:35.111
> !MESSAGE [startIAC: Error Stream] RAServer generated the following output:
> ACServer: error while loading shared libraries: libtptpUtils.so.4:
> cannot open shared object file: No such file or directory
>
> !ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 08:13:37.197
> !MESSAGE [startIAC: Output Stream] RAServer generated the following
> output: ACServer failed to start.
>
> A find for 'libtptpUtils*' shows the file in the following location:
>
> .../eclipse_3.3/plugins/
> org.eclipse.tptp.platform.ac.linux_ia32_4.4.0.v200706020100/
> agent_controller/lib/libtptpUtils.so.4.4.0
>
> (there's also a 64-bit version, but I'm running a 32-bit OS).
>
> Clicking Test for Availablity pauses (where it didn't before) and gives
> the same error dialog:
>
> "An unexpected error occurred while attempting to establish a connection"
>
> However, the reason and details are still blank. No new information is sent
> to the .log file.
>
> I looks like the runtime is expecting to find libtptpUtils.so.4 rather
> than libtptpUtils.so.4.4.0. I created a symlink (libtptpUtils.so.4 ==>
> libtptpUtils.so.4.4.0) in the same lib directory and reran Eclipse.
>
> The .log file now shows that libtptpLogUtils.so.4 is missing.
> libtptpUtils.so.4 was found. symlinking this file (libtptpLogUtils.so.4
> ==> libtptpLogUtils.so.4.4.0) resolves this error and results in
> libtptpConfig.so.4 being missing.
>
> Is there a configuration file in Eclipse somewhere that defines what
> versions of native libraries are to be loaded? Could that file be
> incorrectly configured?
>
> I could symlink all the libraries, but surely there's a better way to fix
> this....?
>
> Thank you for the assist.
>
> -=< tom >=-
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102600 is a reply to message #102513] Tue, 03 July 2007 13:40 Go to previous messageGo to next message
Tom Funk is currently offline Tom FunkFriend
Messages: 22
Registered: July 2009
Junior Member
Hi, Joe,

Thank you for chiming in.

> From your post, I infer that you updated an existing Eclipse install
> rather than installing a new Europa eclipse, but I can't be certain of
> that.

Actually, the new Europa version when into .../eclipse_3.3/, right
next to the previous installation at .../eclipse3.2.1/. I tend to create
new installations for all of my new eclipse installs.

> I'm sorry for the problems you are having with TPTP.

Thank you.

> The scenarios you describe should work out of the box,

Such was my hope... ;-)

> and in our testing scenarios, they do. We will do whatever we can to
> help you get unblocked.

Thanks.

> For the first step, please start with a clean
> install (downloading a Europa package from eclipse.org and then
> installing TPTP -- using the update manager should work fine.)

I've done that, essentially, but just to be sure, I'll start over. I've
kept the Europa Eclipse d/l. I'll start with that.

> I also (always) suggest that when you install a new major
> version of eclipse, you start with a new workspace.

Ouch. ... but I'm game

> You can import any existing projects into that new workspace
> (you lose no data),

Aaaahhh... Why didn't I think of that...?

Does my Mylar (Mylyn) data import, too?

> but the workspace also contains metadata from the
> old eclipse plugins that may not be applicable for your new eclipse
> install.

Do a new eclipse install and new Workspace, with import of the old project.

I'm on it. Will let you know how it goes.

> Thanks for your interest in TPTP.

Thank you for the help.

-=< tom >=-
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102626 is a reply to message #102572] Tue, 03 July 2007 13:44 Go to previous messageGo to next message
Tom Funk is currently offline Tom FunkFriend
Messages: 22
Registered: July 2009
Junior Member
Hey, Joe,

> Did you unzip the AC download on a different machine and then copy the
> bits to your Linux box?

Negative. In this case, the previous message was in response to using the
TPTP All-in-one. I unzipped it into yet another directory (not the
previous 3.3 directory nor the previous 3.2.1 version)

> If you unzip the install using "unzip" on the
> Linux box, the symlinks are created automatically.

I did that.

However, per your previous message, I'm going to start over
with the Europa d/l, using the update manager to pull in TPTP on a new
workspace.

Will report back.

Thanks again.

-=< tom >=-
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102635 is a reply to message #102572] Tue, 03 July 2007 14:00 Go to previous messageGo to next message
Tom Funk is currently offline Tom FunkFriend
Messages: 22
Registered: July 2009
Junior Member
Joe,

I just thought of something. It may explain the problem.

> If you unzip the install using "unzip" on the
> Linux box, the symlinks are created automatically.

Obviously, the symlinks already exist in the zip file. However, are these
symlinks relative to the plug-in directory or relative to the eclipse root
directory?

I ask because when I install (unzip) eclipse, I usually rename the newly
created "eclipse" directory to "eclipse_v.v.v", where "v.v.v" is the
version (i.e., eclipse_3.2.1, eclipse_3.3, etc.). This puts the plugins
and features directories directly under "eclipse_3.3" rather "eclipse."

If the synlinks are relative to ./eclipse/plugins, rather than just
../plugins, this might explain the problem. (iow, ./eclipse_3.3/plugins
breaks the symlinks).

I can test this...

-=< tom >=-
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102664 is a reply to message #102600] Tue, 03 July 2007 15:15 Go to previous messageGo to next message
Joe Toomey is currently offline Joe ToomeyFriend
Messages: 79
Registered: July 2009
Member
Hi Tom,

> Does my Mylar (Mylyn) data import, too?

You can export your Mylyn/Mylar task data using File -> Export -> Mylyn
-> Task Data and then reimport it into your new workspace using the
analogous Import action. When I moved from Mylar to Mylyn, my task data
was correctly imported into Mylyn even though I exported from Mylar
(thank you Mik!)

> I'm on it. Will let you know how it goes.

Please do. Thanks,
--Joe
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102675 is a reply to message #102635] Tue, 03 July 2007 15:20 Go to previous messageGo to next message
Joe Toomey is currently offline Joe ToomeyFriend
Messages: 79
Registered: July 2009
Member
Tom Funk wrote:
> If the synlinks are relative to ./eclipse/plugins, rather than just
> ./plugins, this might explain the problem. (iow, ./eclipse_3.3/plugins
> breaks the symlinks).
>
> I can test this...

I like the theory. AFAIK, there's nothing about the way the symlinks
are created in the zip file that would cause this (they are all relative
to the directory they reside in.) I'm not sure if the rename itself
could invalidate the symlinks or not. It would definitely be
interesting to learn if things work correctly before you rename, and if
so, we can do some more digging to understand why.

Thanks,
--Joe
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102689 is a reply to message #102513] Tue, 03 July 2007 15:59 Go to previous messageGo to next message
Tom Funk is currently offline Tom FunkFriend
Messages: 22
Registered: July 2009
Junior Member
Hi, Joe,

So, I did a clean Europa install (without renaming the eclipse
directory) w/an Update Manager installation of TPTP into a new
workspace.

Results, in a nutshell: same as before.

In the new workspace, I created a new project (did NOT import the old
project) that spawns some chatty threads, waits for keyboard input and
quits. Simple and clean. This test app executes from both the run and debug
environments. Eclipse was started with the -clean argument. I installed no
plugins or features other than Eclipse Europa and TPTP.

For the Eclipse preferences, I took all default settings. When
configuring the Profile environment, I took all defaults.

I don't think I can get a configuration more "Out of the box" than this.

When I click "Check for Availability," I get the following for the details
in the "One of the selected delegates has failed" error dialog:

=============[ start .log ]==================
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.

java.lang.NullPointerException
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.hasProcessTerminated(AutoStartStop.java:275 )
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:113)
at org.eclipse.tptp.platform.execution.client.core.internal.Nod eImpl.connect(NodeImpl.java:117)
at org.eclipse.tptp.platform.jvmti.client.internal.launcher.uti l.AgentControllerDelegate$1$EstablishConnection.run(AgentCon trollerDelegate.java:155)
at java.lang.Thread.run(Thread.java:595)

I checked the Integrated Agent Controller settings. It's enabled and the
JRE matches the the Eclipse JRE (1.5.0_11-b03).

Here's the <workspace>/.metadata/.log file (it's long) The repeated
sessions are from debugging the test app. The entries starting at or
after 10:56 would be the errors generated from configuring and starting
TPTP:

!SESSION 2007-07-03 10:03:39.346 -----------------------------------------------
eclipse.buildId=I20070625-1500
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86 -clean -data /home/tfunk/Projects/java/VL_Trunk_WS

!ENTRY org.eclipse.ui 4 4 2007-07-03 10:10:39.498
!MESSAGE Invalid preference page path: Cache
!SESSION 2007-07-03 10:26:13.798 -----------------------------------------------
eclipse.buildId=I20070625-1500
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86 -clean -data /home/tfunk/Projects/java/VL_Trunk_WS

!ENTRY org.eclipse.update.configurator 2007-07-03 10:56:53.561
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.update.configurator 2007-07-03 10:56:53.610
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.update.configurator 2007-07-03 10:56:53.613
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.update.configurator 2007-07-03 10:56:53.674
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.update.configurator 2007-07-03 10:56:53.678
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 10:56:54.188
!MESSAGE java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
!STACK 0
java.io.IOException: java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:101)
at org.eclipse.hyades.internal.execution.local.control.NodeImpl .connect(NodeImpl.java:283)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.in secureConnect(BaseConnectUtil.java:369)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:255)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:540)
at org.eclipse.tptp.platform.common.ui.trace.internal.util.PDCo reUtil.profileConnect(PDCoreUtil.java:827)
at org.eclipse.tptp.trace.ui.internal.launcher.deleg.applicatio n.PIDelegateHelper$JVMVersionDetector.run(PIDelegateHelper.j ava:473)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.tptp.platform.common 1 0 2007-07-03 10:56:54.189
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.hasProcessTerminated(AutoStartStop.java:275 )
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:113)
at org.eclipse.hyades.internal.execution.local.control.NodeImpl .connect(NodeImpl.java:283)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.in secureConnect(BaseConnectUtil.java:369)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:255)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:540)
at org.eclipse.tptp.platform.common.ui.trace.internal.util.PDCo reUtil.profileConnect(PDCoreUtil.java:827)
at org.eclipse.tptp.trace.ui.internal.launcher.deleg.applicatio n.PIDelegateHelper$JVMVersionDetector.run(PIDelegateHelper.j ava:473)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 10:56:54.203
!MESSAGE java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
!STACK 0
java.io.IOException: java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:101)
at org.eclipse.hyades.internal.execution.local.control.NodeImpl .connect(NodeImpl.java:283)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.in secureConnect(BaseConnectUtil.java:369)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:255)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:540)
at org.eclipse.tptp.platform.common.ui.trace.internal.util.PDCo reUtil.profileConnect(PDCoreUtil.java:827)
at org.eclipse.tptp.trace.ui.internal.launcher.deleg.applicatio n.PIDelegateHelper$JVMVersionDetector.run(PIDelegateHelper.j ava:473)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.tptp.platform.common 1 0 2007-07-03 10:56:54.203
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.hasProcessTerminated(AutoStartStop.java:275 )
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:113)
at org.eclipse.hyades.internal.execution.local.control.NodeImpl .connect(NodeImpl.java:283)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.in secureConnect(BaseConnectUtil.java:369)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:255)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:540)
at org.eclipse.tptp.platform.common.ui.trace.internal.util.PDCo reUtil.profileConnect(PDCoreUtil.java:827)
at org.eclipse.tptp.trace.ui.internal.launcher.deleg.applicatio n.PIDelegateHelper$JVMVersionDetector.run(PIDelegateHelper.j ava:473)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 10:57:07.500
!MESSAGE java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
!STACK 0
java.io.IOException: java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:101)
at org.eclipse.tptp.platform.execution.client.core.internal.Nod eImpl.connect(NodeImpl.java:117)
at org.eclipse.tptp.platform.jvmti.client.internal.launcher.uti l.AgentControllerDelegate$1$EstablishConnection.run(AgentCon trollerDelegate.java:155)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 10:57:07.551
!MESSAGE java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
!STACK 0
java.io.IOException: java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:101)
at org.eclipse.tptp.platform.execution.client.core.internal.Nod eImpl.connect(NodeImpl.java:117)
at org.eclipse.tptp.platform.jvmti.client.internal.launcher.uti l.AgentControllerDelegate$1$EstablishConnection.run(AgentCon trollerDelegate.java:173)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 10:57:32.885
!MESSAGE java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
!STACK 0
java.io.IOException: java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:101)
at org.eclipse.tptp.platform.execution.client.core.internal.Nod eImpl.connect(NodeImpl.java:117)
at org.eclipse.tptp.platform.jvmti.client.internal.launcher.uti l.AgentControllerDelegate$1$EstablishConnection.run(AgentCon trollerDelegate.java:155)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 10:57:32.893
!MESSAGE java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
!STACK 0
java.io.IOException: java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:101)
at org.eclipse.tptp.platform.execution.client.core.internal.Nod eImpl.connect(NodeImpl.java:117)
at org.eclipse.tptp.platform.jvmti.client.internal.launcher.uti l.AgentControllerDelegate$1$EstablishConnection.run(AgentCon trollerDelegate.java:173)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.hyades.trace.ui 4 4 2007-07-03 10:57:32.973
!MESSAGE Agent Controller is unavailable under port 10002. Make sure that the service is started and the port number is correct under preferences.
!STACK 1
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:123)
at org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.connectToAgentController(TIDelegateHelper.java :395)
at org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.launch(TIDelegateHelper.java:308)
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:1153)
at org.eclipse.tptp.trace.ui.provisional.launcher.PrimaryLaunch Delegate.run(PrimaryLaunchDelegate.java:196)
at java.lang.Thread.run(Thread.java:595)
org.eclipse.core.runtime.CoreException[0]: java.lang.NullPointerException
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.hasProcessTerminated(AutoStartStop.java:275 )
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:113)
at org.eclipse.tptp.platform.execution.client.core.internal.Nod eImpl.connect(NodeImpl.java:117)
at org.eclipse.tptp.platform.jvmti.client.internal.launcher.uti l.AgentControllerDelegate$1$EstablishConnection.run(AgentCon trollerDelegate.java:155)
at java.lang.Thread.run(Thread.java:595)
!SUBENTRY 1 org.eclipse.hyades.trace.ui 4 0 2007-07-03 10:57:32.973
!MESSAGE Agent Controller is unavailable under port 10002. Make sure that the service is started and the port number is correct under preferences.
!STACK 0
java.lang.NullPointerException
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.hasProcessTerminated(AutoStartStop.java:275 )
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:113)
at org.eclipse.tptp.platform.execution.client.core.internal.Nod eImpl.connect(NodeImpl.java:117)
at org.eclipse.tptp.platform.jvmti.client.internal.launcher.uti l.AgentControllerDelegate$1$EstablishConnection.run(AgentCon trollerDelegate.java:155)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.ui 4 4 2007-07-03 11:04:55.728
!MESSAGE Invalid preference page path: Cache

=============[ end .log ]==================

Doing ls -l on .../agent_controller/bin/ACStart.sh shows that the execute
bit is NOT set:

~$ ls -l .../agent_controller/bin/ACStart.sh
-rw-r--r-- 1 tfunk tfunk 1714 2007-07-03 10:25 .../agent_controller/bin/ACStart.sh

So, I set the execute bit...

~$ chmod u+x .../agent_controller/bin/ACStart.sh
~$ ls -l .../agent_controller/bin/ACStart.sh
-rwxr--r-- 1 tfunk tfunk 1714 2007-07-03 10:25 .../agent_controller/bin/ACStart.sh

....deleted the previous .log file and restarted Eclipse.

I opened the Profile dialog, went to the Monitor tab and clicked "Check
availability." I got the "An unexpected error occurred while trying to
establish a connnection" error dialog with no reason and no details.
Here's the new .log file:

=============[ start .log ]==================
!SESSION 2007-07-03 11:32:42.367
-----------------------------------------------
eclipse.buildId=I20070625-1500
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line
arguments: -os linux -ws gtk -arch x86 -clean -data
/home/tfunk/Projects/java/VL_Trunk_WS

!ENTRY org.eclipse.update.configurator 2007-07-03 11:33:08.806
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.update.configurator 2007-07-03 11:33:08.853
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.update.configurator 2007-07-03 11:33:08.858
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.update.configurator 2007-07-03 11:33:08.913
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.update.configurator 2007-07-03 11:33:08.918
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 11:33:09.272
!MESSAGE [startIAC: Error Stream] RAServer generated the following output: [: 46: ==: unexpected operator

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 11:33:09.272
!MESSAGE [startIAC: Error Stream] RAServer generated the following output: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: 59: ACServer: Permission denied

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 11:33:11.293
!MESSAGE [startIAC: Output Stream] RAServer generated the following output: ACServer failed to start.
=============[ end .log ]==================

So, now we have permissions problems.

Let's run eclipse as root (using sudo).

I select Open Profile Dialog..., and choose the Monitor tab. It opens
immediately, without pause. This time, the previous filter is not checked.
I check it, select Java Profiling and click Check Availability. The empty
error dialog opens immediately and the .log file now looks like this:

=============[ start .log ]==================
!SESSION 2007-07-03 11:41:38.686
-----------------------------------------------
eclipse.buildId=I20070625-1500
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line
arguments: -os linux -ws gtk -arch x86 -clean -data
/home/tfunk/Projects/java/VL_Trunk_WS

!ENTRY org.eclipse.update.configurator 2007-07-03 11:42:01.146
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.update.configurator 2007-07-03 11:42:01.192
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.update.configurator 2007-07-03 11:42:01.195
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.update.configurator 2007-07-03 11:42:01.344
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.update.configurator 2007-07-03 11:42:01.358
!MESSAGE Can't find bundle for base name feature, locale en_US

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 11:42:01.410
!MESSAGE java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
!STACK 0
java.io.IOException: java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:101)
at org.eclipse.hyades.internal.execution.local.control.NodeImpl .connect(NodeImpl.java:283)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.in secureConnect(BaseConnectUtil.java:369)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:255)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:540)
at org.eclipse.tptp.platform.common.ui.trace.internal.util.PDCo reUtil.profileConnect(PDCoreUtil.java:827)
at org.eclipse.tptp.trace.ui.internal.launcher.deleg.applicatio n.PIDelegateHelper$JVMVersionDetector.run(PIDelegateHelper.j ava:473)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.tptp.platform.common 1 0 2007-07-03 11:42:01.411
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.hasProcessTerminated(AutoStartStop.java:275 )
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:113)
at org.eclipse.hyades.internal.execution.local.control.NodeImpl .connect(NodeImpl.java:283)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.in secureConnect(BaseConnectUtil.java:369)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:255)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:540)
at org.eclipse.tptp.platform.common.ui.trace.internal.util.PDCo reUtil.profileConnect(PDCoreUtil.java:827)
at org.eclipse.tptp.trace.ui.internal.launcher.deleg.applicatio n.PIDelegateHelper$JVMVersionDetector.run(PIDelegateHelper.j ava:473)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 11:42:01.427
!MESSAGE java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
!STACK 0
java.io.IOException: java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:101)
at org.eclipse.hyades.internal.execution.local.control.NodeImpl .connect(NodeImpl.java:283)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.in secureConnect(BaseConnectUtil.java:369)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:255)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:540)
at org.eclipse.tptp.platform.common.ui.trace.internal.util.PDCo reUtil.profileConnect(PDCoreUtil.java:827)
at org.eclipse.tptp.trace.ui.internal.launcher.deleg.applicatio n.PIDelegateHelper$JVMVersionDetector.run(PIDelegateHelper.j ava:473)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.tptp.platform.common 1 0 2007-07-03 11:42:01.428
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.hasProcessTerminated(AutoStartStop.java:275 )
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:113)
at org.eclipse.hyades.internal.execution.local.control.NodeImpl .connect(NodeImpl.java:283)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.in secureConnect(BaseConnectUtil.java:369)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:255)
at org.eclipse.hyades.security.internal.util.BaseConnectUtil.co nnect(BaseConnectUtil.java:540)
at org.eclipse.tptp.platform.common.ui.trace.internal.util.PDCo reUtil.profileConnect(PDCoreUtil.java:827)
at org.eclipse.tptp.trace.ui.internal.launcher.deleg.applicatio n.PIDelegateHelper$JVMVersionDetector.run(PIDelegateHelper.j ava:473)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 11:42:10.932
!MESSAGE java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
!STACK 0
java.io.IOException: java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:101)
at org.eclipse.tptp.platform.execution.client.core.internal.Nod eImpl.connect(NodeImpl.java:117)
at org.eclipse.tptp.platform.jvmti.client.internal.launcher.uti l.AgentControllerDelegate$1$EstablishConnection.run(AgentCon trollerDelegate.java:155)
at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-07-03 11:42:10.946
!MESSAGE java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
!STACK 0
java.io.IOException: java.io.IOException: /home/tfunk/bin/eclipse/eclipse/plugins/org.eclipse.tptp.pla tform.ac.linux_ia32_4.4.0.v200706020100/agent_controller/bin /ACStart.sh: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at org.eclipse.tptp.platform.iac.administrator.internal.startst op.AutoStartStop.startIAC(AutoStartStop.java:101)
at org.eclipse.tptp.platform.execution.client.core.internal.Nod eImpl.connect(NodeImpl.java:117)
at org.eclipse.tptp.platform.jvmti.client.internal.launcher.uti l.AgentControllerDelegate$1$EstablishConnection.run(AgentCon trollerDelegate.java:173)
at java.lang.Thread.run(Thread.java:595)
=============[ end .log ]==================

Joe, I've noticed from other posts that you use Windows. Do you also use
Linux?

Note that mine is a Kubuntu installation, which means a tightly controlled
execution environment where root doesn't exist, and I'm running KDE rather
than Gnome as the window manager. However, also note that I've unzipped to
a directory I own (~/bin/Eclipse). So, I shouldn't be getting permission
errors...

I remain stumped.

-=< tom >=-
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102714 is a reply to message #102513] Tue, 03 July 2007 16:42 Go to previous messageGo to next message
Tom Funk is currently offline Tom FunkFriend
Messages: 22
Registered: July 2009
Junior Member
More updates on this TPTP issue.

ACStart.sh has a syntax error at line 46:

if [ x$TEMP == x ]; then

You're looking for a zero-length string. This syntax is another way to do
this:

if [ -z "$TEMP" ]; then

Also, when I looked at the directory where this script file loves, NONE of
the executables have their execute bits set:

~/bin/<snipped>/agent_controller/bin$ ls -l
total 352
-rw-r--r-- 1 tfunk tfunk 69497 2007-07-03 10:25 ACServer
-rwxr--r-- 1 tfunk tfunk 1714 2007-07-03 10:25 ACStart.sh
-rw-r--r-- 1 tfunk tfunk 1073 2007-07-03 10:25 ACStop.sh
-rw-r--r-- 1 tfunk tfunk 413 2007-07-03 10:25 ACVersion.sh
-rw-r--r-- 1 tfunk tfunk 14373 2007-07-03 10:25 ChkPass
-rw-r--r-- 1 tfunk tfunk 69497 2007-07-03 10:25 RAServer
-rw-r--r-- 1 tfunk tfunk 1714 2007-07-03 10:25 RAStart.sh
-rw-r--r-- 1 tfunk tfunk 1073 2007-07-03 10:25 RAStop.sh
-rw-r--r-- 1 tfunk tfunk 15823 2007-07-03 10:25 readme.txt
-rw-r--r-- 1 tfunk tfunk 21858 2007-07-03 10:25 SampleClient
-rw-r--r-- 1 tfunk tfunk 1306 2007-07-03 10:25 SetConfig.sh
-rw-r--r-- 1 tfunk tfunk 29448 2007-07-03 10:25 TimeCollector
-rw-r--r-- 1 tfunk tfunk 36015 2007-07-03 10:25 tptpFileTransferAgent
-rw-r--r-- 1 tfunk tfunk 55870 2007-07-03 10:25 tptpProcessController

So, I set the execute bit for all but readme.txt and restarted Eclipse.

NOW when I click Check Availability, I get "The connection was successful."

I ran the app, collected some stats and quit. It works just fine. It's a
beautiful thing.

Since I made two changes (syntax and execute bits), we can't really tell
which change fixed the root problem. However, I suspect it's the execute
bits that made the difference.

This is a problem that would be unique to Linux installations; Windows
doesn't have the notion of an execute bit.

To replicate this, you'll need a Linux client installation. Don't think
you'll have to get as specific as "Kunbuntu 7.04 on IA32." Any client-side
Linux should do, really.

I'm guessing that when the Update Manager is unzipping the downloaded zip
files, it's not setting the execute bit on the files in this directory
when it unzips them. It could also be that the execute bit isn't captured
when the zip files are created during the build.

Next steps for me are to import my existing projects and try again. If I
have any more problems, I'll let you know.

Thanks so much for the help, Joe.

-=< tom >=-
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102740 is a reply to message #102675] Tue, 03 July 2007 17:15 Go to previous messageGo to next message
Tom Funk is currently offline Tom FunkFriend
Messages: 22
Registered: July 2009
Junior Member
Tom Funk wrote about broken symlinks
and Joe responded:
> I like the theory. AFAIK, there's nothing about the way the symlinks
> are created in the zip file that would cause this (they are all relative
> to the directory they reside in.)

Thought I'd test this.

After I got the installation working, I renamed the eclipse home
directory from eclipse to eclipse_3.3.0. After restarting eclipse, I got
errors.

The monitor didn't load, so I tried to start if from the Monitor tab of
the Profile configuration dialog. It through an error.

I didn't look too closely at the errors, but it involved
org.eclipse.tptp.jvtmi. Renaming the eclipse home directory breaks the
installation -- at least it does if you rename AFTER getting the
installation working.

I reset the directory name back to eclipse from eclipse_3.3.0 and
restarted eclipse.

It's still broken.

I'm going to start over again, with eclipse_3.3.0 as the eclipse home
directory. I'll use the new workspace.

At least this time I know how to fix it.

-=< tom >=-
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102820 is a reply to message #102714] Tue, 03 July 2007 19:00 Go to previous messageGo to next message
Joe Toomey is currently offline Joe ToomeyFriend
Messages: 79
Registered: July 2009
Member
Hi Tom,

I primarily develop in Windows, but I test on both RHEL 4 and SuSE 9, as
do most of the TPTP project committers. For my part of the testing of
the 4.4 release, I tested both IAC and full AC on SuSE 9 and RHEL 4,
however, I did not test the IAC with bits installed by the update
manager -- only with bits installed from the zip files. Apparently I am
far from alone in that distinction... :-(

I have reproduced this issue and have filed a defect to get this
corrected. Feel free to add yourself to the CC list.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=195303

Regarding the syntax error in ACStart.sh, I can't reproduce this. The
code is the same as you have pasted, but it runs correctly (at least for
me.) The script should be run by /bin/sh -- it's not clear to me why
this would be a syntax error for you on Kunbuntu when it is not for me
on SuSE and RHEL. If it's a bug, we'd like to fix it -- I'd just like
to understand why first.

Thanks for helping to run this down, Tom,
--Joe

Tom Funk wrote:
> More updates on this TPTP issue.
>
> ACStart.sh has a syntax error at line 46:
>
> if [ x$TEMP == x ]; then
>
> You're looking for a zero-length string. This syntax is another way to do
> this:
>
> if [ -z "$TEMP" ]; then
>
> Also, when I looked at the directory where this script file loves, NONE of
> the executables have their execute bits set:
>
> ~/bin/<snipped>/agent_controller/bin$ ls -l
> total 352
> -rw-r--r-- 1 tfunk tfunk 69497 2007-07-03 10:25 ACServer
> -rwxr--r-- 1 tfunk tfunk 1714 2007-07-03 10:25 ACStart.sh
> -rw-r--r-- 1 tfunk tfunk 1073 2007-07-03 10:25 ACStop.sh
> -rw-r--r-- 1 tfunk tfunk 413 2007-07-03 10:25 ACVersion.sh
> -rw-r--r-- 1 tfunk tfunk 14373 2007-07-03 10:25 ChkPass
> -rw-r--r-- 1 tfunk tfunk 69497 2007-07-03 10:25 RAServer
> -rw-r--r-- 1 tfunk tfunk 1714 2007-07-03 10:25 RAStart.sh
> -rw-r--r-- 1 tfunk tfunk 1073 2007-07-03 10:25 RAStop.sh
> -rw-r--r-- 1 tfunk tfunk 15823 2007-07-03 10:25 readme.txt
> -rw-r--r-- 1 tfunk tfunk 21858 2007-07-03 10:25 SampleClient
> -rw-r--r-- 1 tfunk tfunk 1306 2007-07-03 10:25 SetConfig.sh
> -rw-r--r-- 1 tfunk tfunk 29448 2007-07-03 10:25 TimeCollector
> -rw-r--r-- 1 tfunk tfunk 36015 2007-07-03 10:25 tptpFileTransferAgent
> -rw-r--r-- 1 tfunk tfunk 55870 2007-07-03 10:25 tptpProcessController
>
> So, I set the execute bit for all but readme.txt and restarted Eclipse.
>
> NOW when I click Check Availability, I get "The connection was successful."
>
> I ran the app, collected some stats and quit. It works just fine. It's a
> beautiful thing.
>
> Since I made two changes (syntax and execute bits), we can't really tell
> which change fixed the root problem. However, I suspect it's the execute
> bits that made the difference.
>
> This is a problem that would be unique to Linux installations; Windows
> doesn't have the notion of an execute bit.
>
> To replicate this, you'll need a Linux client installation. Don't think
> you'll have to get as specific as "Kunbuntu 7.04 on IA32." Any client-side
> Linux should do, really.
>
> I'm guessing that when the Update Manager is unzipping the downloaded zip
> files, it's not setting the execute bit on the files in this directory
> when it unzips them. It could also be that the execute bit isn't captured
> when the zip files are created during the build.
>
> Next steps for me are to import my existing projects and try again. If I
> have any more problems, I'll let you know.
>
> Thanks so much for the help, Joe.
>
> -=< tom >=-
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102893 is a reply to message #102820] Tue, 03 July 2007 22:27 Go to previous messageGo to next message
Tom Funk is currently offline Tom FunkFriend
Messages: 22
Registered: July 2009
Junior Member
Howdy, Joe,

> Regarding the syntax error in ACStart.sh, I can't reproduce this.

Huh.

> The code is the same as you have pasted, but it runs correctly (at least
> for me.) The script should be run by /bin/sh --

Maybe a bash thing...?

> it's not clear to me
> why this would be a syntax error for you on Kunbuntu when it is not for
> me on SuSE and RHEL.

I know. Me either. Just eyeballing the old syntax, it should work. The log
file for that issue is long gone.

I'll keep my eyes peeled for it, thought.

Look for a new thread re: timeout, btw... :-(

Thanks for the help.

-=< tom >=-
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #102987 is a reply to message #102689] Wed, 04 July 2007 12:21 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: n.sherlock.gmail.com

Tom Funk wrote:
> So, I did a clean Europa install (without renaming the eclipse
> directory) w/an Update Manager installation of TPTP into a new
> workspace.

I've done the same things as you, and am having the exact same symptoms,
but my platform is totally different: Windows XP and JRE 1.6. Bizarre.

Is there somewhere that the IAC logs messages to that isn't
..metadata/.log (Which is clear of any errors)?

Cheers,
Nicholas Sherlock
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #103034 is a reply to message #102987] Wed, 04 July 2007 20:13 Go to previous messageGo to next message
Tom Funk is currently offline Tom FunkFriend
Messages: 22
Registered: July 2009
Junior Member
Hi, Nicholas,

> I've done the same things as you, and am having the exact same symptoms,
> but my platform is totally different: Windows XP and JRE 1.6. Bizarre.

As I understand it from this group and copious Google searches, TPTP isn't
ready for Java 1.6. There's been some informal use of 1.6 by some of the
committers, but all the posts that mention JRE 1.6 say the same thing:
downgrade to 1.5.

> Is there somewhere that the IAC logs messages to that
> isn't .metadata/.log (Which is clear of any errors)?

Not that I know of -- that that's hardly conclusive. I'm new at this whole
TPTP thing.

-=< tom >=-
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #105715 is a reply to message #102820] Thu, 19 July 2007 08:41 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: arodriguez.atmel.com

On Tue, 03 Jul 2007 15:00:19 -0400, Joe Toomey wrote:
> Regarding the syntax error in ACStart.sh, I can't reproduce this. The
> code is the same as you have pasted, but it runs correctly (at least for
> me.) The script should be run by /bin/sh -- it's not clear to me why
> this would be a syntax error for you on Kunbuntu when it is not for me
> on SuSE and RHEL. If it's a bug, we'd like to fix it -- I'd just like
> to understand why first.

A quick look at the /bin/sh symlink on ubuntu 7.04 shows that it links to
/bin/dash - Debian Almquist SHell. I'm betting that /bin/sh links to
/bin/bash on SuSE and RHEL (and probably any other non-debian derivate).
dash requires the shell script to be POSIX compliant, while bash is less
strict and supports the '==' operator for string comparison.

I tested changing the "#!/bin/sh" to "#!/bin/bash" and the script runs
without any error. And, as Tom has pointed out, changing the line to "if [
-z "$TEMP" ]; then" will also work. The latter might be the better
solution.


Regards,
Alex
Re: Major issues with Eclipse 3.3 and TPTP 4.4 [message #107304 is a reply to message #102740] Thu, 02 August 2007 10:29 Go to previous message
Paul Slauenwhite is currently offline Paul SlauenwhiteFriend
Messages: 975
Registered: July 2009
Senior Member
Tom,
This appears to be a defect in the JVMTI tooling. Can you open a bug
report in the TPTP Profiling product and Platform.Agents.JVMTI component:

https://bugs.eclipse.org/bugs/enter_bug.cgi?classification=T PTP

Paul
"Tom Funk" <tdfunk@nettally.com> wrote in message
news:f6e06r$rsg$6@build.eclipse.org...
> Tom Funk wrote about broken symlinks
> and Joe responded:
>> I like the theory. AFAIK, there's nothing about the way the symlinks
>> are created in the zip file that would cause this (they are all relative
>> to the directory they reside in.)
>
> Thought I'd test this.
>
> After I got the installation working, I renamed the eclipse home
> directory from eclipse to eclipse_3.3.0. After restarting eclipse, I got
> errors.
>
> The monitor didn't load, so I tried to start if from the Monitor tab of
> the Profile configuration dialog. It through an error.
>
> I didn't look too closely at the errors, but it involved
> org.eclipse.tptp.jvtmi. Renaming the eclipse home directory breaks the
> installation -- at least it does if you rename AFTER getting the
> installation working.
>
> I reset the directory name back to eclipse from eclipse_3.3.0 and
> restarted eclipse.
>
> It's still broken.
>
> I'm going to start over again, with eclipse_3.3.0 as the eclipse home
> directory. I'll use the new workspace.
>
> At least this time I know how to fix it.
>
> -=< tom >=-
Previous Topic:download site down?
Next Topic:Running AGR as an in-process strategy
Goto Forum:
  


Current Time: Tue Apr 16 10:25:33 GMT 2024

Powered by FUDForum. Page generated in 0.08920 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top