Bug 5802 – adjust default termination time in globusrun-ws in GT4.2

Bug 5802 - adjust default termination time in globusrun-ws in GT4.2

Summary:

adjust default termination time in globusrun-ws in GT4.2

Status:	RESOLVED FIXED

Product:	GRAM
Component:	wsrf gram clients
Version:	4.1.2
Platform:	Macintosh All

Importance:	P3 normal
Target Milestone:	4.2
Assigned To:	Joe Bester

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-01-21 16:31 by Martin Feller
Modified:	2008-02-05 13:32 (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 Feller 2008-01-21 16:31:00

There is a change in lifetime handling in ws-gram in GT 4.2 as described
in the attached document at 
http://www.globus.org/mail_archive/gram-dev/2008/01/msg00000.html

It makes probably sense to not set a default lifetime in globusrun-ws
anymore in case the client didn't specify any lifetime.
By this the job will run to completion and will stay alive for
a while afterwords (as the admin configured in the new JNDI configuration
parameter jobTTLAfterProcessing (default 24h), but will expire and get
removed afterwards.

The new code of ws-gram can be found in branch ws-gram-bug5247.

------- Comment #1 From Joe Bester 2008-02-05 13:32:50 -------

Committed fix for this to ws-gram-bug5247 branch.

Joe