GT 4.0.1 Incremental Release Notes

Table of Contents

Introduction
Obtaining and Installing Software
Documentation
Support
Licensing
Summary of Changes Since 4.0.0
Common Runtime Components
Security
Data Management
Information Services
Execution Management
Cross-component Tools
All Fixed Bugs Since 4.0.0
Common Runtime Components
Security
Data Management
Information Services
Execution Management
Cross-component Tools
Known Problems As of 4.0.1
Common Runtime Components
Security
Data Management
Information Services
Execution Management
Cross-component Tools
Release Notes by Component

Introduction

The GT4 development team is pleased to make 4.0.1 available for download. This incremental release includes important fixes for bugs reported against version 4.0.0 of the Globus Toolkit (GT4). Highlights of release 4.0.1 include:

This page describes only the fixes since the 4.0.0 release; for details regarding 4.0.0 go to: http://www.globus.org/toolkit/releasenotes/4.0.0/.

Obtaining and Installing Software

To download this release, go to the 4.0.1 Download page.

For information on installing this release, go to the 4.0 Installation Guide.

Documentation

Use the existing documentation for 4.0, which starts at http://www.globus.org/toolkit/docs/4.0/. For more information about how our new documentation is structured, please see the new Documentation Overview.

Support

An overview on GT support can be found here.

Licensing

The Globus Toolkit is distributed and licensed for use under the terms of the Apache License, Version 2.0.

To view the licenses of the 3rd party software used by the developers of the Globus Toolkit, click here.

Summary of Changes Since 4.0.0

Common Runtime Components

The following changes have occurred for Java WS Core:

  • globus-deploy-gar now supports -backup option to create a backup of existing service configuration files during deployment.
  • The standalone container when stopped by pressing Ctrl-C will now perform the same cleanup operation as when stopped using the globus-stop-container tool.
  • The local UDP ports used for sending out the usage statistics information in Java can now be controlled via the GLOBUS_UDP_SOURCE_PORT_RANGE environment variable.
  • Axis notification handling was improved to use a thread pool for firing notifications instead of starting a new thread for each notification. Also, the memory overhead associated with each notification was reduced.
  • The standalone container will now use ~/.globus/persisted/<ip>-<port>/ directory to store its persistent information. Under Tomcat the ~/.globus/persisted/<ip>-<webapp.name>/ directory will be used instead. This change enables to easily run multiple standalone containers as the same user on the same machine without any conflicts or to have multiple deployments of Java WS Core (as different web applications) in the same Tomcat installation.
  • Improved Tomcat deployment and support. Also, ContainerConfig.getBaseDirectory() and ContainerConfig.getSchemaDirectory() API were defined to return the appropriate directory locations depending on the container type. Also, auto flush functionality was added to the Tomcat HTTPS connector code to enable interoperability between a C client and Tomcat 5.0.x.
  • Proper WS-Addressing headers are now added to the SOAP Fault messages. Please see Bug 3614 for details.

The following changes have occurred for C WS Core.

  • New implementation of WS-Secure Messaging.
  • Handler data structures changes slightly to accomodate WS-Secure Messaging implementation.
  • Client bindings now include doxygen documentation blocks which can be used to generate API documentation
  • Improved XML parsing, especially of floating-point numbers and arbitrary-precision integers
  • New attribute to include verbose error messages from the XML parser.
  • Improved handling of GPT metadata by the C bindings generator.

The following changes have occurred for Python WS Core:

  • Added "defer" attribute to generated client bindings. If set to "True" method invocations return a twisted deferred instance, else if set to "False" (default) they return an instance representing the response message. Thus it's easy to switch between asynchronous and synchronous programming paradigms.
  • New resources can be dropped into the service container at runtime as twisted "rpy" scripts. So resources (eg. CounterService) are added or removed from the service container by simply adding or removing a rpy script (eg. CounterService.rpy).
  • WS-BaseNotification, added support for pausing and resuming subscriptions through the Subscription Manager.
  • WS-ResourceProperties operations QueryResourceProperties and GetMultipleResourceProperties are now supported/implemented in generated service stubs.

Other than a bug fix, there were no changes for XIO.

No changes have occurred for C Common Libraries.

Security

The following change has occurred for Community Authorization Service (CAS):

  • CAS service was tested and necessary changes was made (to register with Index service) to ensure it deploys and runs with Apache Tomcat.

No changes have occurred for the Delegation Service.

Other than bug fixes, no changes have occurred for Message/Transport-level security.

No changes have occurred for WS Authorization Framework.

Other than bug fixes, no changes have occurred for Pre-Web Services Authorization & Authentication.

The following changes have occurred for MyProxy:

  • Updated GPT package from 1.17 to 2.3.
  • Fixed myproxy-init compatibility with Java CoG grid-proxy-init in PATH (using grid-proxy-init -hours instead of -valid).
  • Fixed error message on server-side authorized_renewers check.
  • Added client-side reverse lookup on server IP address for authorization consistency with other GSI clients.
  • Added native PAM support (not requiring SASL).
  • Added support for managing trusted CA certificates using myproxy-logon/myproxy-retrieve -T option
  • Added the myproxy-replicate utility for managing multiple myproxy-server repository replicas for high availability.
  • Added myproxy_version() and myproxy_check_version() functions to verify headers match the shared library in use.
  • Fixed bug in 1.17 that caused myproxy-get-delegation not to be included in binary GPT installs.
  • Use system getopt_long() if available; otherwise, use included getopt_long from NetBSD instead of GNU version as previous.
  • Fixed server side bug where the default_key_retrievers policy was always applied even if the credential had a key retriever policy.
  • Fixed myproxy_get_delegation() signature to maintain API-level compatibility.
  • Added dynamic buffer management for improved handling of large messages.

No changes have occurred for SimpleCA.

No changes have occurred for GSI-OpenSSH.

The SweGrid Accounting System (SGAS) is a new tech preview available with the 4.0.1 release.

Data Management

The following change has occurred for RFT:

  • RFT database schema has been updated to make it work with mySQL and other databases. All these changes are backwards compatible.

The following change has occurred for GridFTP:

  • A protocol change was made to match a wuftpd extension regarding listings. This resolved an issue with a function in the Java Cog Kit. This breaks technical protocol compatibility with RFC959 (FTP), but matches the behavior of 2.4.x servers. See Bug 3507 for details.

Other than bug fixes, no changes have occurred for RLS.

No OGSA-DAI WSRF-specific changes have been made for this release.

The following general OGSA-DAI changes have been made for this release:

  • Core OGSA-DAI functionality (the engine and data resource connection classes) has been abstracted out into a service-level independent module. OGSA-DAI OGSI, WSI and WSRF share exactly the same core code. Core OGSA-DAI functionality and activities are now Globus-independent.
  • The namespaces of OGSA-DAI configuration, Perform and Response documents have been completely changed:
    • Perform and response documents are now declared within the http://ogsadai.org.uk/namespaces/2005/03/types namespace.
    • Data resource and activity configuration documents and roleMap documents are now declared within the http://ogsadai.org.uk/namespaces/2005/03/config namespace.
  • The deliverToStream activity now delivers to a URL of form http://HOST:PORT/WEBAPP/servlet/DeliverToStreamServlet?url=http://HOST:PORT/WEBAPP/ogsadai/DataService&streamId=NAME - gsh has been renamed to url.
  • Control flow constraints can now be expressed within Perform documents. This means you can ensure that one activity will not start until another has completed e.g. ensuring that a new table is not filled with data until it has been created.
  • Server-side exceptions outwith client control and authorisation failures have been refactored. The problems are logged in detail server-side and tagged with a unique ID. This ID, with a request to contract the service deployer, is returned to the client.
  • All OGSA-DAI data services now provide a getVersion operation which returns the OGSA-DAI flavour and version number.
  • GUI installation tools now allow required JARs to be selected via a file browser.
  • GUI installation tools now render yes/no options as check boxes.

As a technical preview release the Data Replication Service (DRS) has undergone numerous changes to its schema, exceptions, and API. We do not expect the interfaces to change as dramatically between this release and the next full release. Changes since the GT 4.0.0 release of DRS include:

  • Rewrite of the WSDL and Schema
  • Refactoring of the backend implementation into a reusable JNDI resource
  • Support for "bulk" operations on the RLS for discovery and registration of replicas
  • Concurrent querying of all replica catalogs (LRCs) to locate all available replicas efficiently
  • Splitting of RFT transfer requests into configurable-sized chunks to avoid SOAP message size limitations
  • Introduction of source selector interfaces to allow user-defined source selection algorithms
  • New set of command-line tools to fully exploit all DRS operations as defined by its WSDL
  • DRS service now downloads (via http, ftp) remotely-hosted request files to avoid SOAP message size limitations
  • Support for fine-grained lifecycle control via start, stop, suspend, and resume operations
  • Replicator resource is no longer backed by database persistence to avoid DBMS setup
  • Extensize set of configuration options to tune DRS behavior
  • Support for all RFT options (e.g., tcp buffer size, parallelism, etc.)

Information Services

The following features have been added to the WS MDS Aggregator component:

  • Two additional configuration options have been added to the AggregatorConfiguration JNDI bean type that allow administrators more control over when notifications are sent out to listeners that have subscribed to the service group 'Entry' resource property. These changes consist of two boolean parameters, "notifyOnEntryLifetimeExtension" and "notifyOnEntryContentChange". By default, if the parameters are not supplied, "notifyOnEntryLifetimeExtension" is set to TRUE and "notifyOnEntryContentChange" is set to FALSE. The "notifyOnEntryLifetimeExtension" parameter causes a notification to be generated whenever a service group entry is added, removed, or refreshed. The "notifyOnEntryContentChange" causes a notification to be generated whenever an entry has is aggregate content updated. The syntax for specifying these configuration parameters is as follows: 

          <resource name="configuration"
                type="org.globus.mds.aggregator.impl.AggregatorConfiguration"> 
      ...
                      
      <parameter>
	<name>notifyOnEntryLifetimeExtension</name>
	<value>true</value>
      </parameter>  
      <parameter>
	<name>notifyOnEntryContentChange</name>
	<value>false</value>
      </parameter>
      
      ...
      </resource>

  • An additional configuration option has been added to the AggregatorConfiguration JNDI bean type to allow adminstrators to configure the interval in milliseconds at which the the service group's sweeper thread purges out stale registrant entries. The syntax for specifying the sweeper interval is: 

     
    <resource name="configuration"
                 type="org.globus.mds.aggregator.impl.AggregatorConfiguration"> 
    ...
                            
    <parameter>
      <name>entrySweeperInterval</name>
      <value>120000</value>
    </parameter>
    
    ...
    </resource>

  • An additional configuration option has been added to the AggregatorConfiguration JNDI bean type to allow adminstrators to specify a developer supplied callback function that will be invoked when a service group entry is removed from the service group. See the API documentation for the AggregatorServiceGroupEntryRemovedCallback interface for implementation details. 

        <resource name="configuration"
                 type="org.globus.mds.aggregator.impl.AggregatorConfiguration"> 
    ...
                    
    <parameter>
      <name>entryRemovedCallback</name>
      <value>org.globus.mds.aggregator.impl.SampleAggregatorRemoveCallback</value>
    </parameter>
    
    ...
    </resource>

Other than bug fixes, no changes have occurred for WS MDS Index service.

Other than bug fixes, no changes have occurred for Pre-WS MDS.

Other than bug fixes, no changes have occurred for WS MDS Trigger service.

Other than bug fixes, no changes have occurred for WebMDS.

Execution Management

The following change has occurred for WS-GRAM:

  • The behavior of relative paths in job description elements was fixed. See Bug 3602.

Other than a bug fix, no change has occurred for Pre-WS GRAM.

The only change that has occurred for the Community Scheduler Framework (CSF) is that it can now submit GRAM jobs to the Queuing service.

No changes have occurred for Globus Teleoperations Control Protocol (GTCP).

The following changes have occurred for the Workspace Management Service (WMS) since 4.0.0 (the tech_preview_4 release is included):

  • Persistence was added, workspaces persist after container reboots
  • (optional) support for multiple workspaces per credential was added
  • The service will no longer compile without a separate download (see admin guide)
  • A queryPDP for use with other services (e.g., GRAM) was added
  • A banlistPDP was added for the workspace service itself, which allows a site to ban particular DNs and attributes (as well as ban clients from adding these entities to workspace access and management policies)

Cross-component Tools

The following changes have occurred for JGlobus module of Java CoG Kit.

  • Added support for auto flush functionality to GssOutputStream.
  • Made GlobusURL to ignore white spaces (in front or the back) of the string URL argument.
  • Added support for controlling local (source) ports of TCP and UDP sockets. The source ports can be controlled via the GLOBUS_TCP_SOURCE_PORT_RANGE and GLOBUS_UDP_SOURCE_PORT_RANGE environment variables. All of the CoG libraries will obey the TCP source port range if set (there is no library in the JGlobus module that currently uses UDP sockets).
  • Added support for AES encrypted private keys.
  • Improved the FTP library: added support for IPv6, NLST, ALLO, and CKSM operations. Also, added API for setting the protection level on the control channel. Exposed a new extendedTransfer function that allows for partial 3rd party transfers. Also, fixed problems handing error conditions involving a data channel.

The following changes have occurred for pyGlobus:

  • Support for new RFC 3820 proxy certificates.
  • A script that generates a configuration file for the unit tests.

All Fixed Bugs Since 4.0.0

Common Runtime Components

The following bugs were fixed for Java WS Core:

  • Bug 2968: Globalization: Error in JUnit execution in the Japanese locale
  • Bug 3216: Tomcat deployment: copy container-log4j.properties file instead of log4j.properties
  • Bug 3217: Get the appropriate base directory location (in Tomcat or in the standalone container) without the need of MessageContext
  • Bug 3218: Tomcat deployment: copy libexec/ directory during the deployment
  • Bug 3250: ConcurrentModificationException during subscription
  • Bug 3257: Improvements to the globus-start-container-detached tool
  • Bug 3302: ReflectionResourceProperty inconsistent handling on remove on Array type
  • Bug 3418: Support for Ant 1.5.1
  • Bug 3466: Error creating persistent directories
  • Bug 3472: Secure Conversation Context creation is not thread safe
  • Bug 3473: ServiceAuthorizationChain bug in setPolicy node import missing
  • Bug 3492: org.globus.wsrf.tools.wsdl.GenerateBinding should use canonical paths for both the bindingFile and serviceFile
  • Bug 3532: Recovery thread dies in Tomcat
  • Bug 3545: NPE in usage statistics code breaks container
  • Bug 3582: globus-stop-container-detached exits with non-0 on successful exit
  • Bug 3600: ServerHost.getBaseURL() sometimes returns a wrong URL
  • Bug 3614: Missing WS-Addressing headers in fault messages and fault logging problems

The following bugs were fixed for C WS Core:

  • Bug 3339: The globus-wsrf-cgen program in the globus_c_wsrf_cgen package creates an empty client bindings library when the -no-client option is passed to it. This results in a compile error on some architectures.
  • Bug 3370: The C WSRF Core perfomance test programs fails if a large number of iterations is used. The problem is an error in the test program.
  • Bug 3395: The globus_js package does not compile on Tru64.
  • Bug 3433: The tests in the globus_c_ws_messaging_test package fail to run when the user's PATH does not contain ".".
  • Bug 3434: The tests in the globus_c_wsrf_resource_test package fail to run when the user's PATH does not contain ".".
  • Bug 3318: SOAP deserializer fails to deserialize xsd:dateTime when the local timezone offset is negative.
  • Bug 2178: SOAP headers used for dispatching operations are not signed when TLS is not used. GT 4.0.1 includes an implementation of WS-Secure message which signs WS-Addressing-related headers as well as SOAP bodies.
  • Bug 2270: Packages generated by globus-wsrf-cgen do not include dependencies from the patch-and-build package metadata.
  • Bug 3275: The generated serialize_contents bindings pass GLOBUS_XSD_ELEMENT_CONTENTS_ONLY to subelements, causing subelement markup to be discarded.
  • Bug 3322: The globus_wsrf_core_create_endpoint_reference() function partially initializes endpoint the endpoint. Applications which use this function may crash when accessing the EPR.
  • Bug 3505: Error compiling globus_c_ws_messaging package on AIX. Error serializing floating-point numbers in XML.
  • Bug 3515: Error compiling test_secure_message_counter.c test program on AIX.

No bugs were fixed for Python WS Core.

The following bug was fixed for XIO:

  • Bug 3410: Reporting an error on writev on some systems

No bugs were fixed for C Common Libraries.

Security

The following bugs were fixed for CAS:

  • Bug 3224: CAS expects objects with exact name matchCAS expects objects with exact name match to be enrolled prior to assertion generation
  • Bug 3243: Issue with revoking rights using cas-rights-admin
  • Bug 3295: Exception when clients are invoked with no parameters

No bugs were fixed for Delegation Service.

The following bugs were fixed for Message/Transport-level security:

  • Bug 3501: Reject limited proxy configuration not honored if Secure Transport is used
  • Bug 3504: Secure notifications fail without default credentials.

The following bug was fixed for WS Authorization Framework:

  • Bug 3528: Action Operation Namespace in SAML Authorization Callout

The following bugs were fixed for Pre-WS Authentication and Authorization:

  • Bug 3553: Error in OLD GAA code with valid signing policy
  • Bug 3564: gss_compare_name has invalid free
  • Bug 3506: openssl does not build with 32bit flavors on opteron
  • Bug 3347: Unexpected messages using grid-default-ca
  • Bug 3127: globus_gsi_gssapi: Authorization denied message needs clarification
  • Bug 3164: Command -"grid-proxy-init" with combined options "-policy" ,"-verify" gives an Error
  • Bug 3180: grid-proxy-init ignores -certdir option if not specified with -verify
  • Bug 3189: grid-mapfile-delete-entry fails to delete single LN
  • Bug 3192: grid-mapfile-delete-entry with dryrun option deletes LN
  • Bug 3179: grid-proxy-info issues

The following bug was fixed for MyProxy:

  • Bug 2939: The MyProxy commands ignore invalid options rather than returning an error message.

No bug fixes were made to SimpleCA.

No bugs were fixed for GSI-OpenSSH.

SweGrid Accounting System (SGAS) is a new tech preview with the 4.0.1 release; therefore, this section does not apply.

Data Management

The following bugs were fixed for RFT:

The following bugs were fixed for GridFTP:

  • Bug 3351: Initialization errors are ignored
  • Bug 3369: globus-gridftp-server single mode operation fails.
  • Bug 3364: authz callback bug in case of negative authorization decisions?
  • Bug 3487: SRB DSI does not authenticate properly with SRB
  • Bug 3453: ~ expansion does not work in CWD argument
  • Bug 3402: Running GridFTP in privilege separation mode on non-Linux platforms
  • Bug 3465: SITE VERSION
  • Bug 3386: hostname and interface options require an ip address
  • Bug 3507: cannot list with jglobus 1.2
  • Bug 3568: list function terminates after 200 files
  • Bug 3608: threaded gridftp hangs on lists (LIST, MLSx)

The following bugs were fixed for RLS:

  • Bug 3186: globus-rls-cli dumps core in interactive mode if args > 100
  • Bug 3223: HP-UX doesnt support TIOCNOTTY ioctl (use POSIX setsid())
  • Bug 3225: build problem+ java rls client always returns invalid handle
  • Bug 3308: RLS Server package not included in Fedora 3 and RH9 binaries
  • Bug 3409: RLS prints out negative thread ids
  • Bug 3493: globus-rls-cli dumps core when odd number of bulk params passed
  • Bug 3494: globus-rls-cli passes invalid value for odd numbered bulk command

No OGSA-DAI WSRF-specific bug fixes have been made for this release.

The following general OGSA-DAI bug fixes have been made for this release:

  • Client toolkit now raises an authorisation error if roleMapping fails server-side.
  • sqlQueryStatement activity can now retrieve BLOB or IMAGE fields from databases.
  • GridFTP-related delivery activities have had their JavaDoc, and the associated client toolkit JavaDoc revised to include details about how security credentials are used.
  • WebRowSet processing code for SQL activities no longer has option to make results human-readable.
  • Perform document schema property provided by OGSA-DAI service now includes required import statements.
  • Response documents constructed in-code now meet the Response document XML Schema.
  • User doc front page now includes link to JavaDoc in binary distributions.
  • Errors in stringTokenizerActivity JavaDoc have been corrected.
  • Various user doc revisions and corrections have been made.
  • GUI installation tools now no longer occasionally freeze.
  • Installation tools now no longer need to edit the Tomcat server configuration file so problems with its location or format no longer arise.

Significant improvements to the stability, scalability and usability of the DRS service have been made since the initial introduction of the DRS in the GT 4.0.0 release. Detailed tracking of bugs and corresponding fixes will begin with this release.

Information Services

The following bugs were fixed for WS MDS ServiceGroup:

  • Bug 3500: ServiceGroupRegistrationClient.terminate( ) failure
  • Bug 3470: Unregister functionality missing in ServiceGroupRegistrationClient?

The following bugs were fixed for WS MDS Aggregator:

  • Bug 3393: Notifications need to be sent by an AggregatingServiceGroupResource when registrants successfully update the terminationTime of a member AggregatingServiceGroupEntryResource
  • Bug 3177: AggregatingServiceGroup EntrySweeper interval needs to be user configurable
  • Bug 3150: AggregatingServiceGroup* needs to provide Resource.RemoveCallback for entry resources (or equivalent functionality) for derived code

The following bug was fixed for the WS MDS Index Service:

  • Bug 3570: wsdl error while extending IndexPortType

The following bugs were fixed for Pre-WS MDS:

  • Bug 3437: shell test uses "==" instead of "=" for AIX uname comparison
  • Bug 3441: MDS info provider fails to gather network info on Tru64

The following bugs were fixed for the WS MDS Trigger Service:

  • Bug 3489: Trigger's minimumFiringInterval is not working properly
  • Bug 3488 Trigger's minimumMatchTime is not working
  • Bug 3468: Trigger unable to process boolean result
  • Bug 3467: Trigger unable to process numerical result

The following bugs were fixed for WebMDS:

  • Bug 3160: Format summary line for RLS
  • Bug 3537: WebMDS security -- remote users can determine some information about local files
  • Bug 3617: Some xsl files missing from webmds filelist

Execution Management

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 bug was fixed for Pre-WS GRAM:

  • Bug 3589: Pre-WS GT4 globusrun -a mode cores on a USATLAS site

No bug was fixed for the Community Scheduler Framework (CSF).

The following bugs were fixed for Message/Transport-level security:

  • Bug 3501: Reject limited proxy configuration not honored if Secure Transport is used
  • Bug 3504: Secure notifications fail without default credentials.

No bugs were fixed for Globus Teleoperations Control Protocol (GTCP).

No bugs were fixed for Workspace Management Service (WMS).

Cross-component Tools

The following bugs were fixed for JGlobus module of the Java CoG Kit:

  • Bug 3194: Support for controlling local (source) ports ranges for TCP and UDP sockets
  • Bug 3329: Support for AES encrypted private keys
  • Bug 3486: FTP library problems handling error conditions involving data channel

No bugs were fixed for pyGlobus.

Known Problems As of 4.0.1

Common Runtime Components

The following problems and limitations are known to exist for Java WS Core at the time of the 4.0.1 release:

  • Limitations

    • WS-Notification support:

      • Only the Simple topic dialect is supported (others can be added)
      • Only flat topic spaces are supported (architecture does allow for more advanced structures)
      • Actions on the precondition, selector and policy fields in a subscription are not supported
      • When a resource is removed its subscriptions are not removed automatically
    • Only XPath resource property queries are supported (others can be added)
    • A resource might not get destroyed at the exact time as indicated by the scheduled termination time. A sweeper thread that removes expired resources runs periodically (every 1 minute by default) so an expired resource might not get removed until the next time the sweeper thread runs.
    • SOAP messages with attachments are not supported. In fact, the Axis version distributed with GT was compiled without attachment support.
    • In certain cases, the "dialect" attribute of TopicExpression or QueryExpression is not serialized properly as defined in the schema. An "org.globus.dialect.attr.qualified" Java system property was added to control how the serialization of the dialect attribute. Please see the Bug 3513 for details.

  • Known Bugs

    • Bug 2471: Message security signature verification issues
    • Bug 2445: Same input and output messages in WSDL confuse Axis
    • Bug 2921: Support for TerminationTimeChangeRejectedFault
    • Bug 2926: Local transport does not work without a current MessageContext
    • Bug 3113: Processing by the WSDLPreprocessor produces output different depending on the JVM
    • Bug 3482: wsa:From is not set correctly when service calls another service
    • Bug 3483: xsd:anyType not serialized correctly

The following problems are known to exist for C WS Core at the time of the 4.0.1 release:

  • SOAP faults without header elements are not parsed correctly.
  • Multiple schemas which use the same namespace prefixes can confuse the WSDL parser.
  • Nillable elements are not serialized or deserialized correctly if the element does not contain the minOccurs="0" attribute
  • Errors that occur when processing resource properties on systems which crash when the printf format %s is matched with a null parameter will crash the c service container.

No problems are known to exist for Python WS Core at the time of the 4.0.1 release.

There are no known problems with XIO at the time of the 4.0.1 release.

The following problems are known to exist for C Common Libraries at the time of the 4.0.1 release:

  • Bug 484: Mem leak on deactivate_all
  • Bug 686: globus_mutex_lock() behaves differently on Unix -vs- Win32
  • Bug 930: inttypes.h included without testing if it's present
  • Bug 1141: Misleading error messages using globus-makefile-header
  • Bug 2315: Globus common fails to compile if there is no ipv6 support
  • Bug 2791: Command globus-domainname needs g11n
  • Bug 2793: Command globus-generalized-time needs g11n
  • Bug 2794: Command globus-hostname needs g11n
  • Bug 2801: Command globus-version needs g11n
  • Bug 3081: Small leak in libltldl
  • Bug 3107: Fatal error: tcp_init(): globus_io_tcp_create_listener() ...
  • Bug 3350: globusrun-ws hangs for 2 minutes at startup
  • Bug 3380: doxygen-related scripts belong in core?
  • Bug 3392: globusrun-ws Bus error
  • Bug 3427: Issues with permission of file testcred.pem located in gl...
  • Bug 3436: globus_uuid MAC address retrieval doesn't work on solaris
  • Bug 3509: GLOBUS_COMMON_MODULE->GLOBUS_CALLBACK_MODULE deactivation...
  • Bug 3610: globus-makefile-header returns bad field

Security

The following problem is known to exist for CAS at the time of the 4.0.1 release:

  • Bug 3371: cas-group-admin delete fails if grant all rights is given to the same group that was created.

No new problems are known to exist for the Delegation Service.

No new problems are known to exist for Message/Transport-level security.

No new problems are known to exist for WS Authorization Framework.

No problems are known to exist for Pre-WS Authentication & Authorization at the time of the 4.0.1 release.

The following problem is known to exist for MyProxy at the time of the 4.0.1 release:

  • Bug 2709: The MyProxy package isn't internationalized.

There are no new known problems for SimpleCA.

No problems are known to exist for GSI-OpenSSH at the time of the 4.0.1 release.

SweGrid Accounting System (SGAS) is in tech preview and as such it is not deemed as a "final product" at this stage. We welcome any comments and suggestions for improvements (which you may send to swegrid-accounting@pdc.kth.se).

Data Management

No problems are known to exist for RFT at the time of the 4.0.1 release.

The following problems are known to exist for GridFTP at the time of the 4.0.1 release:

  • Bug 3324: gridftpd croaking on startup - globus_l_io_tcp_contact_string failed
  • Bug 3214: Backend of GT4 GridFTPd should ignore ~/.globus/certificates
  • Bug 3387: client library doesn't respect GLOBUS_HOSTNAME
  • Bug 3618: GridFTP fails to transfer a file if I've only group permissions
  • Bug 3622: gridftp server improperly handles detach option in config file

The following problems are known to exist for RLS at the time of the 4.0.1 release:

  • Threading/Libc Problems: set LD_ASSUME_KERNEL=2.2.5 in your environment and see Platform Notes for more information.
  • Bug 2601: Missing 'sigset' linking error
  • Bug 2821: GT3.9.5: jni.h not found when compiling RLS on MacOS X
  • Bug 3215: RLS client portability improvements
  • Bug 3253: GT4 build fails on Mac OS X 10.4 Tiger
  • Bug 3403: SQL_NO_DATA not supported for searched update/delete SQL calls *PostgreSQL only* (PATCH AVAILABLE)

The following problems are known to exist for OGSA-DAI at the time of the 4.0.1 release:

  • Problems retrieving BLOBS

    When trying to retrieve BLOBs from a relational database you will get zero rows returned (or an error). The following error message will be logged: 

    Base64Provider has not been set up with a Base64 implementation

    This will be fixed in the next release. In the meantime if you have the source version of the release, you can correct this bug by changing two files and rebuilding OGSA-DAI. See BLOB Error Workaround for details.

  • DeliverToStream activity is broken.

    The DeliverToStream activity has a bug in the WSRF implementation. The service URL passed to the servlet is 'null' rather than the correct URL.

    Thus where the documentation says the data will be available from a URL of the form:

    http://host:port/ogsa/servlet/DeliverToStreamServlet?url= http://host:port/ogsa/ogsadai/DataService&streamId=NAME

    It will actually be available from a URL in the form:

    http://host:port/ogsa/servlet/DeliverToStreamServlet?url=null&streamId=NAME

    This will be fixed for the next release.

  • Client toolkit asynchronous result set broken.

    The ResultSet object returned by the OutputStreamActivity class' getResultSet methods do not work for WSRF 1.0. This is because the code attempts to use the getNBlocks service operation which is not implemented in WSRF 1.0. This will be fixed in our next release.

    There are two possible work arounds to this problem:

    1. Use synchronous delivery. The ResultSet returned by the SQLQuery activity's getResultSet() method does work.
    2. Alter the client toolkit code to use the getBlock() service operation. Unfortunately this option will be very slow as only one row will be retrieved at a time.

The following problem is known to exist for DRS at the time of the 4.0.1 release:

  • Bug 3502: Container freezes (CPU spin) when making remote call between ws-resources. See record for WORKAROUND.

Information Services

There are no known problems with the WS MDS Aggregator API at the time of the 4.0.1 release.

No known problems exist for the WS MDS Index service at the time of the 4.0.1 release

No known problems exist for Pre-WS MDS at the time of the 4.0.1 release.

    No problems are known to exist for the WS-MDS Trigger service at the time of the 4.0.1 release.

    The following problems are known to exist for WebMDS at the time of the 4.0.1 release:

    Execution Management

    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

    No problems are known to exist for Pre-WS GRAM at the time of the 4.0.1 release.

    There are no known problems for the Community Scheduler Framework (CSF) at the time of the 4.0.1 release.

    No problems are known to exist for Globus Teleoperations Control Protocol (GTCP) at the time of the 4.0.1 release.

    No problems are known to exist for the Workspace Management Service (WMS) at the time of the 4.0.1 release.

    Cross-component Tools

    The following problems are known to exist for JGlobus module of the Java CoG Kit at the time of the 4.0.1 release:

    • Bug 1056: FTP client in extended block mode after receiving EODC does not wait for EOD on the same channel
    • Bug 2277: GridFTPClient bug Parallel, Passive, EBlockImageDCReader does not receive EOF
    • Bug 2345: Allow for a way to set cert and key location using environment variables
    • Bug 2413: A rare decrypt error
    • Bug 3299: Extended Key Usage certificate extension not supported

    There are no known problems to exist for pyGlobus at the time of the 4.0.1 release.

    Release Notes by Component