Table of Contents
These release notes are for the incremental release 4.0.6. It includes a summary of changes since 4.0.5, bug fixes since 4.0.5 and any known problems that still exist at the time of the 4.0.6 release. This page is in addition to the top-level 4.0.6 release notes at http://www.globus.org/toolkit/releasenotes/4.0.6.
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.5.
However, WS GRAM users could benefit from the RFT connection caching improvement in this release. For example, a Condor-G user submitting 1000 jobs that do file staging (no matter the file size) to the same WS GRAM service would benefit from the RFT enhancement. When submitting jobs with file staging or file cleanup directives, WS GRAM will use RFT to get that work done. If there are jobs for the same user that use the same two GridFTP servers, then RFT will cache that connection and reuse it for multiple jobs. This saves the effort of connecting, authenticating, authorizing for each file transfer. Performance tests showed improvements of around 30% and improved reliability. For this reason, 4.0.6 is highly recommended for WS GRAM users that make use of file staging and cleanup directives.
- Bug 989:Error message I get when 'grid-proxy-init' is all that's needed
- Bug 3726:GlobusRun error message typo
- Bug 3910:Bad permissions on condor log file prevents job submissions
- Bug 4908:Stage out failes in JobManager.pm
- Bug 4968:WS-Notification error: java.lang.ClassCastException: org.globus.exec.generated.StateChangeNotificationMessageWrapperType cannot be cast to org.w3c.dom.Element
- Bug 4984:Change in behaviour in usage of client-generated job resource keys
- Bug 5020:implementation of myceil in pbs.pm
- Bug 5032:Staging information removed from the perl description.
- Bug 5080:performance configuration doc section
- Bug 5363:UUID cache cleanup
- Bug 5395:Locally invoked services seem to get initialized twice with local invocations in a recovery situation
- Bug 5425:Backwards compatability break in 4.0.5
- Bug 5439:GramJob fails in destruction of deleg. creds of subjobs in a multijob
- Bug 5457:Misbehaviour of globus-gridmap-and-execute
- Bug 5511:Review synchronization in MJFS.createManagedJob()
- Bug 5514:Error in subject creation in LocalInvocationHelper
- Bug 5597:LocalInvocationHelper: wrong way of getting container configuration values
- Bug 5696:too generic error message by globus-job-manager-script.pl
- Bug 5760:Run JobManagerScript without creating a thread
- Bug 3310:Inconsistency across components with respect to client command behavior.
- Bug 3865:Enhance RSL with Job Name
- Bug 3866:Support for parametric or array job types
- Bug 3892:Out of date performance data?
- Bug 3912:Rotation of gram_condor_log?
- 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 4684:Loading persisted jobs with expired delegation resources causes stacktraces
- Bug 4751:GRAM2 GRAM4 Performance Comparison
- Bug 4787:no lifetime management for WS Rendezvous
- Bug 4790:stdout RP gets null
- Bug 4824:feature request: configurability of location where service writes PBS job scripts
- Bug 4833:command line program for service audit info
- Bug 4836:job submitted INFO level logging
- Bug 4864:environment variables containing '=' get escaped
- 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 5012:Container in livelock state for an incorrectly mapped DN
- Bug 5112:submitting job error
- Bug 5120:submitting job error with PBS
- Bug 5348:Missing documentation for job recovery information
- Bug 5397:GRAM4 recovery of persisted job resources needs to be reviewed
- Bug 5405:custom extensions in WS GRAM
- Bug 5414:Add globus_wsrf_gram_client_tools to 4.0 branch for 4.0.6
- Bug 5471:GRAM Jobs Hang in Unsubmitted State
- Bug 5525:Add support for OSC mpiexec (not MPICH2 command!) to PBS adapter
- Bug 5611:GramJob API changes to improve performace and efficiency
- Bug 5617:GRAM4 seg hangs with fork jobs
- Bug 5698:Allow a prologue/epilogue script for 'mpi' and 'multiple' jobs
- Bug 5711:globusrun-ws error with -term +HH:MM option
- 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 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
Click here for more information about this component.