Bug 3458 – globusrun-ws isn't automatically releasing holds

Bug 3458 - globusrun-ws isn't automatically releasing holds

Summary:

globusrun-ws isn't automatically releasing holds

Status:	RESOLVED FIXED

Product:	GRAM
Component:	wsrf gram clients
Version:	4.0.0
Platform:	PC Linux

Importance:	P1 major
Target Milestone:	4.0.2
Assigned To:	Joe Bester

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-06-08 13:16 by Peter Lane
Modified:	2005-11-08 15:45 (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 Peter Lane 2005-06-08 13:16:01

When a hold is specified in the job description, globusrun-ws should be
releasing it automatically in interactive mode when a state notification
indicates the hold is in effect to avoid deadlock.

This is different from setting and releasing CleanUp holds for streaming.  That
functionality is working fine.

------- Comment #1 From Joe Bester 2005-11-08 15:45:30 -------

Committed fixes to gt4 branch and trunk. Added test cases to the gram scheduler
test package.

joe