Bugzilla – Bug 1585
job output empty if job takes more than 5 minutes
Last modified: 2005-12-05 17:30:13
You need to
before you can comment on or make changes to this bug.
When I submit a job using Java CoG to a remote machine, and the job takes more
than 5 minutes before it produces any output, then any subsequent output is lost.
To replicate it, submit a simple shell script like
It happens with fork jobmanager on several platforms (Linux/IA-32, Irix/MIPS).
On several machines with the same OS/CPU, it happens only on some of them, but
on the machines where the problem occurs, it occurs always. So it is
machine-dependent and deterministic.
However it doens't happen with native "globusrun" client.
The default timeout for all socket was is set to 5 minutes. I added API to
modify the timeout. Also, updated the GassServer in globusrun program to have
no timeout and updated the Gram callback handlers to have a timeout of their