Bug 1585 - job output empty if job takes more than 5 minutes
: job output empty if job takes more than 5 minutes
Status: RESOLVED FIXED
: CoG jglobus
gram
: 1.1a
: All All
: P2 normal
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2004-02-20 08:35 by
Modified: 2005-12-05 17:30 (History)


Attachments


Note

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


Description From 2004-02-20 08:35:42
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

sleep 360
ls -l

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.
------- Comment #1 From 2004-02-20 14:02:54 -------
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 
credential.