Community
Participate
Working Groups
1. Install the Agent Controller Runtime (tested on Linux-IPF) 2. Run SetConfig and ACStart 3. Run SampleClient as described in the getting_started section "Checking Agent Controller Installation" An error is returned "Connected to the Agent Controller on "localhost" at port number 10006 ERROR: Unable to get agent org.eclipse.tptp.TimeCollector Press any key to exit..." From the servicelog: "<CommonBaseEvent creationTime="2007-12-20T18:31:36.078913Z" globalInstanceId="A76AB5080001342D3A9F8DBD17E6A37F" msg="PC startProcess: Error (6006), invalid executable '.\Tim eCollector.exe'" severity="50" version="1.0.1">"
The problem is fairly simple. The agent.xml files under /agents/ in the Linux (IA32, EM64T, IPF) builds contain improper Windows-specific .EXE references. Each of the Linux builds need to have the following line replaced, for each affected agent: From: <launchInfo><Application executable=".\TimeCollector.exe"></Application></launchInfo> To: <launchInfo><Application executable="./TimeCollector"></Application></launchInfo> E.g. replacing the windows-only backslash and ".exe" with the proper Unix forward slash and executable name. This must be done on the agent.xml file in the "org.eclipse.tptp.FileTransferAgent" and "org.eclipse.tptp.TimeCollector" agent directories.
Hi Kiryl, can you make the appropriate changes to the Linux builds? Thanks!
This Linux specific problem is known and documented in AC's bin/readme.txt (but not in /getting_started.html). This document proposes to edit TimeCollector agent.xml manually before running SampleClient. As it is not user friendly I am agree that problem is to be fixed. Currently I see three possible solutions: 1) have two versions of agent.xml files in CVS repository for Windows and Linux and pack appropriate file according to target OS 2) continue to have one agent.xml file in CVS repository but dynamically edit it by packaging scripts 3) continue to have one agent.xml file with cross-platform form of path to agent application and make AC enough smart to run application having such path (say have "./TimeCollector" instead of ".\TimeCollector.exe") Notes by solutions: (1) It is simplest but produces problems of supporting two versions of the same file (2) I do not like it as dynamic editing of agent.xml by packaging script may be not reliable especially if content/format of agent.xml will be changed in future (3) Taking into account that AC is cross-platform product, I like this way while it is not the easiest By the way there is a related bug 132407 which propose fourth way. It is dynamic generation of agent.xml by SetConfig script during AC configuration phase. I would like to do short investigation of the solution (3) in order to implement it.
My investigation showed that solution (3) is not such easy. So I have implemented solution (2).
To be verified.
Verified on TPTP-4.5.0-200802100400.
*** Bug 132407 has been marked as a duplicate of this bug. ***
