Re: [geclipse-dev] Job statuses 64, 128

[Mariusz Wojtysiak <mariusz.wojtysiak@xxxxxxxxxxxxx>]

Romain napisał(a):
> job https://wms.pnpi.nw.ru:9000/64BM7rMghM4AvWB2ilFgcw updated, status 
> 128

IGridJobStatus.UNKNOWN = 0x80

UNKNOWN means that status for job cannot be obtained because of some
temporary problems (e.g. broken internet connection, job service is down
etc).


> job https://grid-lb1.desy.de:9000/mkwIR6AfJcRFv_9E8baeKw updated, 
> status 64

IGridJobStatus.UNDEF = 0x40

Status of the job cannot be determined. Javadoc says:
The difference between UNDEF and UNKNOWN is that UNKNOWN is a temporary
state (e.g. because some network problem) and UNDEF is more permanent state
(e.g. status cannot be retrieved because there is no access to status
service like no appropriate plugin is available) Job with status UNKNOWN
will be queried again during the session, job wit status UNDEF will not.
UNDEF job existing in the workspace will be queried for update when gEclipse
starts

I checked our sources and found that UNDEF in wrongly mapped from gLite
status PURGED. So the most probably your job was purged on grid.

I will create a bug that gLite status PURGED should be mapped to gEclipse
status PURGED.

Regards,
Mariusz