Table of Contents
These release notes are for the incremental release 4.0.1. It includes a summary of changes since 4.0.0, bug fixes since 4.0.0 and any known problems that still exist at the time of the 4.0.1 release. This page is in addition to the top-level 4.0.1 release notes at http://www.globus.org/toolkit/releasenotes/4.0.1.
For release notes about 4.0 (including feature summary, technology dependencies, etc) go to the WS GRAM 4.0 Release Notes.
The following change has occurred for WS-GRAM:
- The behavior of relative paths in job description elements was fixed. See Bug 3602.
The following bugs were fixed for WS GRAM:
- Bug #3190: Staging jobs are not recoverable
- Bug #3205: globus-scheduler-provider-fork script does not get the correct value for totalnodes
- Bug #3235: Condor SEG seg faults on x86_64
- Bug #3174: globusrun-ws -debug gives seg fault on sles9 x86_64
- Bug #3256: coverability fails in WaitingForStateChanges
- Bug #3114: globusrun-ws should give hints on where the RSL parsing failed
- Bug #3504: Submission without default credential
- Bug #3531: globusrun-ws core dumps with -monitor
- Bug #3544: globusrun-ws using null service path
- Bug #3556: globusrun-ws header deserialization error on destroy
- Bug #3554: SEG not relocatable
- Bug #3586: globusrun-ws can't load secure message handler
- Bug #3590: Arguments with '$' in them cause StringIndexOutOfBoundsException
- Bug #3596: PBS missing check for relative directories
- Bug #3599: Job can restart with internal state "Restart"
- Bug #3598: globusrun-ws -self doesn't work for multi-jobs
- Bug #3602: Relative stdout/err paths should be relative to directory not ${GLOBUS_USER_HOME}
- Bug #3230: test security requires a grid-mapfile entry now
- Bug #3252: PBS scheduler event generator doesn't build on Solaris
- Bug #3292: occasional SEG write failure
- Bug #3301: Default ${GLOBUS_SCRATCH_DIR} is wrong when using ant 1.6.2
- Bug #3309: globusrun-ws usage message incorrect
- Bug #3319: GRAM scheduler tests fail with condor
- Bug #3320: relative directory test and stdin test assume files or directories
- Bug #3442: GRAM should use 'mpiexec' before 'mpirun'
- Bug #3447: PBS SEG generates bad dates
- Bug #3410: globus_xio writev() error
- Bug #3532: Recovery thread dies in Tomcat
- Bug #2730: Job description variable fault lost
- Bug #3132: Staging parameters should be automatically determined if running co located
- Bug #3333: Multijob destruction failure
- Bug #3342: Reliable Job Create isn't entirely reliable
- Bug #3498: simple multi-jobs periodically hangs
- Bug #3524: stdout/err RPs aren't being prefixed with user home
- Bug #3533: notification not fired in Tomcat
- Bug #3526: secManager.credentialToSubject problem
- Bug #3075: Issues with globusrun-ws and -Sf option
- Bug #3397: Misconfiguration of GCC "-Wno-unused" flag for Tru64 native compiler
- Bug #3474: tmp subdir is not world-writable
- Bug #3517: WS-GRAM build failure in 4_0_branch
- Bug #3426: globus-job-manager-script.pl broken on !LD_LIBRARY_PATH platforms
The following problems are known to exist for WS GRAM at the time of the 4.0.1 release:
- High throughput can cause an OutOfMemoryError exception. Fixes will appear in the next development release.
- Bug #2974: Inconsistent Arguments
- Bug #1562: Condor jobs fail when running globus-sh-exec job
- Bug #2527: Add a failure case for non-existant queue to scheduler test suite
- Bug #2049: Batch providers need a namespace
- Bug #2967: Job submission inconsistent behaviour with delegated credential
- Bug #3204: InternalStateEnumeration schema cleanup
- Bug #3238: Not implemented option
- Bug #3185: pbs job manager exit code
- Bug #2951: strange security output from multiob
- Bug #3242: Software selection thru WS GRAM RSL
- Bug #3002: sudo path isn't set correctly in libexec/globus-sh-tools-vars.sh
- Bug #3495: queue information, job count not reported to MDS
- Bug #3529: setup/postinstall fatal errors should be warnings
- Bug #3458: globusrun-ws isn't automatically releasing holds
- Bug #3534: globusrun-ws needs a -release option
- Bug #3384: Inconsistent jobType/count parameter semantics
- Bug #3571: ant not found during install
- Bug #3416: hardcoded jobtypes
- Bug #3575: SEG dependent on GLOBUS_LOCATION env var
- Bug #3579: takes over 4 seconds to start a single job with 4.0.1 branch container
- Bug #3611: get job state and queue information from SEG
Click here for more information about this component.