Bug 5805 – Change threadpools from Gram custom implementation to java.util.concurrent

Bug 5805 - Change threadpools from Gram custom implementation to java.util.concurrent

Summary:

Change threadpools from Gram custom implementation to java.util.concurrent

Status:	RESOLVED WONTFIX

Product:	GRAM
Component:	wsrf managed execution job service
Version:	4.1.2
Platform:	Macintosh All

Importance:	P3 normal
Target Milestone:	---
Assigned To:	Stuart Martin

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-01-21 17:06 by Martin Feller
Modified:	2012-09-05 11:43 (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 17:06:38

Purpose:
* Use feature provided by Java 1.5 instead of using probably worse
  self-written code.
* Enables more controlled shutdown behavior which leads to a much more
  stable recovery situation (currently somewhat uncontrollable)
  and thus improves reliability and stability in a container shutdown
* reduces the cost of persistence operations

Isn't too much work and is probably very worth the effort. Tried it
with code from 4.0.6 and ran a couple of condor-g submissions without
problems.

------- Comment #1 From Stuart Martin 2012-09-05 11:43:40 -------

Doing some bugzilla cleanup...  Resolving old GRAM3 and GRAM4 issues that are
no longer relevant since we've moved on to GRAM5.  Also, we're now tracking
issue in jira.  Any new issues should be added here:

http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363