Bug 1585 – job output empty if job takes more than 5 minutes

Bug 1585 - job output empty if job takes more than 5 minutes

Summary:

job output empty if job takes more than 5 minutes

Status:	RESOLVED FIXED

Product:	CoG jglobus
Component:	gram
Version:	1.1a
Platform:	All All

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Jarek Gawor

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2004-02-20 08:35 by Martin Kuba
Modified:	2005-12-05 17:30 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description From Martin Kuba 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 Jarek Gawor 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.