Bugzilla – Bug 5802
adjust default termination time in globusrun-ws in GT4.2
Last modified: 2008-02-05 13:32:50
You need to
before you can comment on or make changes to this bug.
There is a change in lifetime handling in ws-gram in GT 4.2 as described
in the attached document at
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
The new code of ws-gram can be found in branch ws-gram-bug5247.
Committed fix for this to ws-gram-bug5247 branch.