Bug 5859 - Java GramJob getExitCode() always returns 0
: Java GramJob getExitCode() always returns 0
Status: RESOLVED WONTFIX
: GRAM
wsrf gram clients
: 4.0.3
: All Linux
: P3 normal
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2008-02-11 02:09 by
Modified: 2012-09-05 11:43 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2008-02-11 02:09:43
I've a problem retrieving the exit code of an interactive job submitted using
ws-gram in Java. I submit the job using the GramJob.submit. Then you can use
the job.getExitCode() to retrieve the exit code, but it always returns zero. It
returns zero for for instance the executable 'mkdir' without any arguments,
which should return 1. It also returns zero for non-existing executables
(however, the state changes to failed).

It happens with the FORK and the SGE resource manager, but probably also with
other resource managers, I didn't try that. I'm using GT4.0.3
------- Comment #1 From 2008-02-12 08:06:23 -------
Thanks for this bug report.  Hopefully we'll be able to look into this soon.

-Stu
------- Comment #2 From 2012-09-05 11:43:43 -------
Doing some bugzilla cleanup...  Resolving old GRAM3 and GRAM4 issues that are
no longer relevant since we've moved on to GRAM5.  Also, we're now tracking
issue in jira.  Any new issues should be added here:

http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363