Community
Participate
Working Groups
If the process launched on the remote computer exits in a short period of time (processes like “printenv”, “ls”), the event “processExited” is not raised. I use addProcessListener method of IProcess interface. I always get the “processLaunched’ event, but the event “processExited” fires only when the remote process is quite long, for example “SimpleAppl” from the samples that writes to the console and waits for an input. Then, I tried to add an Event listener to the Agent Controller. But I got no call from the process controller at all. Here is the code. m_agentController.addEventListener("org.eclipse.tptp.processController", new ICommandHandler() { public void incomingCommand(INode node, ICommandElement command) { handleCommand(command); } }); Actually, I need to get an “Exit Code” after the remote process terminates. Is there any way to get it? My platform for the AC: Red Hat Enterprise Linux ES release 3 (Taroon Update 6) My platform for the client in Java: Windows XP, Java Sun 1.4.2_13 Thanks, Michael.
Need the servicelog to help us determine if the process controller is failing to send the processExited event cmd or if the client side isn't receiving it, in the case where the application exits quickly. Please repeat the problem and attach the resulting servicelog.log with debug turned on. (Edit serviceconfig.xml, level="DEBUG" format="Simple"). The application's exit code is included in the processExitedEvent cmd sent to the client, but the client API does not expose that value. Please enter an enhancement request (set component=Platform.Execution.Framework for client API requests). Alternatively, you could write your own cmd handler in order to extract the exit code from the xml cmd.
*** Bug 166834 has been marked as a duplicate of this bug. ***
Assigning to Igor, target 4.4.
This bug is a duplicate of the Bug 165946
Previous comment #4 is incorrect. This bug is a duplicate of the Bug 165948
Guru, the patch fixes the issue in the execution framework. Please review the patch.
*** This bug has been marked as a duplicate of bug 165948 ***
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
