Table of Contents
These release notes are for the incremental release 4.0.8. It includes a summary of changes since 4.0.7, bug fixes since 4.0.7 and any known problems that still exist at the time of the 4.0.8 release. This page is in addition to the top-level 4.0.8 release notes at http://www.globus.org/toolkit/releasenotes/4.0.8.
For release notes about 4.0 (including feature summary, technology dependencies, etc) go to the WS GRAM 4.0 Release Notes.
Other than bug fixes, no changes have been made to WS GRAM since 4.0.7.
However, some improvements have been made to RFT in 4.0.8, which makes this release important for WS GRAM users that submit jobs that include file staging directives.
- Bug 5617:GRAM4 seg hangs with fork jobs
- Bug 5977:Add user's DN to INFO logging statement for each job submision
- Bug 5982:GRAM handles lack of local username badly(java.lang.NullPointerException)
- Bug 5992:delegated user proxy job file is not being removed
- Bug 6036:bad ResourceUnknown error from globusrun-ws
- Bug 6055:WS-GRAM accepts a limited proxy for job execution
- Bug 6068:Section about job lifetime is missing in users guide
- Bug 6070:info about how to disable an already installed LRM adapter is missing
- Bug 6182:Section about Condor specific elements in extensions is missing
- Bug 2629: performance timings in globusrun-ws
- Bug 3310: Inconsistency across components with respect to client command behavior.
- Bug 3529: setup/postinstall fatal errors should be warnings
- Bug 3575: SEG dependent on GLOBUS_LOCATION env var
- Bug 3865: Enhance RSL with Job Name
- Bug 3866: Support for parametric or array job types
- Bug 3892: Out of date performance data?
- Bug 3948: Service must release all of its resources on deactivation
- Bug 4181: Allow File Staging To/From globusrun-ws application without an external server
- Bug 4182: Improve Condor/Fork Job Monitoring for reliability and security
- Bug 4311: GRAM error log files
- Bug 4513: LD_LIBRARY_PATH should not be set if no library_path is specified
- Bug 4550: Multijob code not checking for existence of job credential
- Bug 4761: Scheduler Tutorial is missing WS-GRAM setup package
- Bug 4778: WS-Fork job manager doesn't set environment up for mpi jobs
- Bug 4787: no lifetime management for WS Rendezvous
- Bug 4791: Job state history RP
- Bug 4817: Condor OS and ARCH do not have dynamic defaults
- Bug 4824: feature request: configurability of location where service writes PBS job scripts
- Bug 4833: command line program for service audit info
- Bug 4864: environment variables containing '=' get escaped
- Bug 4918: user account details are cached even for unknown users
- Bug 5012: Container in livelock state for an incorrectly mapped DN
- Bug 5017: gram[24] tests that need to be updated
- Bug 5348: Missing documentation for job recovery information
- Bug 5402: invalid password error messages
- Bug 5433: public interface doc lists non-public/internal APIs
- Bug 5471: GRAM Jobs Hang in Unsubmitted State
- Bug 5515: Destruction of subscription resources in a container shutdown/restart
- Bug 5525: Add support for OSC mpiexec (not MPICH2 command!) to PBS adapter
- Bug 5611: GramJob API changes to improve performace and efficiency
- Bug 5698: Allow a prologue/epilogue script for 'mpi' and 'multiple' jobs
- Bug 5712: Gram auditing: local_job_id format variations
- Bug 5713: GRAM auditing: Failed database connection loses audit records
- Bug 5714: GRAM Auditing: additional data in audit records
- Bug 5725: Gram auditing: housekeeping for the auditRecords database
- Bug 5745: Allow users to specify JDD in a different order than RSL schema
- Bug 5770: GRAM4 auditing: inconsistent data in job_description column of DB
- Bug 5776: GRAM4 auditing: Need for an INFO log message
- Bug 5777: GRAM2 audting: database connection times out
- Bug 5778: GRAM2 audting: no error message on db update failure
- Bug 5805: Change threadpools from Gram custom implementation to java.util.concurrent
- Bug 5820: Improve Condor Logfile Processing in GRAM
- Bug 5859: Java GramJob getExitCode() always returns 0
- Bug 5864: Audit logging field requests
- Bug 5865: Audit logging Usage Records requests
- Bug 5969: GRAM Job submission failed!!!
- Bug 6002: globusrun-ws hangs indefinitely
- Bug 6024: GRAM Audit v2
- Bug 6043: Confusing JobID in timeout message
- Bug 6065: Deleting delegated credential does not work
- Bug 6069: JDD documentation issues
- Bug 6072: specification of RAM per process in parallel jobs
- Bug 6091: GRAM4 JDD substitution detection is too broad
- Bug 6102: GRAM4 throughput tester for 4.2
- Bug 6203: audit record not inserted for RSL argument containing single quotes
- Bug 6204: Drain Mode for the GRAM service
- Bug 6271: Proxy cleanup doesn't check for authz callouts
Click here for more information about this component.