Table of Contents
These release notes are for the incremental release 4.0.5. It includes a summary of changes since 4.0.4, bug fixes since 4.0.4 and any known problems that still exist at the time of the 4.0.5 release. This page is in addition to the top-level 4.0.5 release notes at http://www.globus.org/toolkit/releasenotes/4.0.5.
For release notes about 4.0 (including feature summary, technology dependencies, etc) go to the WS GRAM 4.0 Release Notes.
There are a number of new features and performance improvements in 4.0.5. We highly recommend upgrading to this version over 4.0.4. Since we have these new features, it bears reminding of the policy for them in GT point releases. Interoperability must be maintained and any new features must be turned off by default. That way a user will not be impacted, unless they choose to turn on a new feature.
Below is the list if new features in 4.0.5:
- Bug 5009: globusrun-ws output for bad -Ft is unhelpful (part2)
- Bug 5128: GRAM LSF job monitor uses INT32_MAX (undefined on Tru64 Unix)
- Bug 3841: User home directory should be cached
- Bug 4474: globus-gridmap-and-execute problem with additional PDPs
- Bug 5081: xml extensions naming inconsistencies
- Bug 5334: gram audit DB schemas missing in binary installers
- Bug 4174: GRAM should check for needed Perl modules
- Bug 5383: GRAM recovery: jobs with staging fail if they already passed the staging state.
- Bug 5247:job cancellation can lead to container hanging
- Bug 5363:UUID cache cleanup
- Bug 5397:GRAM4 recovery of persisted job resources needs to be reviewed
- 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 4790:stdout RP gets null
- Bug 4817:Condor OS and ARCH do not have dynamic defaults
- Bug 4859:globusrun-ws staging error after gt4 deployed to tomcat
- Bug 4864:environment variables containing '=' get escaped
- Bug 4874:LRUCache problem during job submission from Condor-G to GRAM4
- Bug 4898:Streaming problem with globusrun-ws
- Bug 4908:Stage out failes in JobManager.pm
- Bug 4918:user account details are cached even for unknown users
- Bug 4944:Multijob resources never yield to memory pressure and can't be destroyed
- Bug 4968:WS-Notification error: java.lang.ClassCastException: org.globus.exec.generated.StateChangeNotificationMessageWrapperType cannot be cast to org.w3c.dom.Element
- Bug 4981:Hundreds of thousands of bogus entries in PBS server logs
- Bug 4984:Change in behaviour in usage of client-generated job resource keys
- Bug 4989:PBS environment var limit not tested
- Bug 5015:null pointer exception when submitting job to nightly build
- Bug 5020:implementation of myceil in pbs.pm
- 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 3529:setup/postinstall fatal errors should be warnings
- Bug 3726:GlobusRun error message typo
- Bug 3910:Bad permissions on condor log file prevents job submissions
- Bug 4684:Loading persisted jobs with expired delegation resources causes stacktraces
- Bug 5017:gram[24] tests that need to be updated
- Bug 3948:Service must release all of its resources on deactivation
- Bug 3384:Inconsistent jobType/count parameter semantics
- Bug 3571:ant not found during install
- Bug 3575:SEG dependent on GLOBUS_LOCATION env var
- Bug 3672:Streaming with PBS fails
- Bug 3803:Default scratchDirectory doesn't exist
- Bug 4216:Empty submit_test/submitxxx.err causes FAILure in Local tests
- Bug 4452:job submission response is effected by java 1.5 thread processing
- Bug 4464:setting the mpirun/exec path used for mpi jobs
- Bug 4533:make-test-script.pl bug
- Bug 4597:Globus/Condor integration issues on HP-UX
- Bug 4719:globus runs /usr/bin/env without checking for \u
- Bug 4734:Missing wsa:Action for GRAM4 rendezvous register operations
- Bug 4749:client receives no state notifications if RSL gram:count is big
Click here for more information about this component.