This is actually the correct behaviour depending on how the LSF job reached EXIT. Finished in BES means that the process completed (with any exit code, non-zero included). Terminated means that the BES Activity was killed with a Terminate operation. This is also indicated by EXIT in LSF, but currently besserver does not look to see if EXIT is a result of a bkill (BES Terminate) operation.
So, the besserver does need to check how the job finished (which is doesn't do now), but it's not as straightforward as LSF EXIT being equivalent to BES Terminated.
I'll leave this tracker open as a reminder to fix the detection of Terminated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=11198
Originator: NO
This is actually the correct behaviour depending on how the LSF job reached EXIT. Finished in BES means that the process completed (with any exit code, non-zero included). Terminated means that the BES Activity was killed with a Terminate operation. This is also indicated by EXIT in LSF, but currently besserver does not look to see if EXIT is a result of a bkill (BES Terminate) operation.
So, the besserver does need to check how the job finished (which is doesn't do now), but it's not as straightforward as LSF EXIT being equivalent to BES Terminated.
I'll leave this tracker open as a reminder to fix the detection of Terminated.
Logged In: YES
user_id=11198
Originator: NO
Sorry ... I just read your original post more carefully.
Yes ... of course it should be terminated ... as I said below, this code has not been added to besserver yet.