GT 4.0.3 Incremental Release Notes

GT 4.0.3 Incremental Release Notes

1. Introduction

The Globus Toolkit development team is providing a new incremental release of the Globus Toolkit 4.0 that includes important security fixes. Users of GT 4.0 are strongly encouraged to install this release. Highlights include:

This page describes only the changes since the 4.0.2 release. For details regarding previous 4.0 releases, see:

2. Obtaining and Installing Software

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

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

3. Documentation

Use the existing documentation for 4.0, which starts at For more information about how our new documentation is structured, please see the new Documentation Overview.

4. Support

An overview on GT support can be found here.

5. 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.

6. Usage Statistics

For full information about usage statistics collected by GT 4.0.3 and how to opt-out, see Usage Statistics Collection by the Globus Alliance.

7. Summary of Changes Since 4.0.2

7.1. Common Runtime Components

7.1.1. Java WS Core

The following changes have occurred for Java WS Core:

  • Adjusted the default size of the thread pool used by the standalone and embedded container. By default the standalone container will now have a minimum of 2 threads and a maximum of 20. The embedded container will now have a minimum of 1 thread and maximum of 3 threads.
  • Refreshed version of CoG JGlobus library. Please see the CoG JGlobus Release Notes for more details.
  • Updated version of Apache Commons CLI 2.0 library.
  • Refreshed version of Apache Axis library with the following bug fixes:

    • Fault bean generation with optional primitive types
    • Rare synchronization problem in symbol table
  • Added more scripts for interop and unit tests to integrate better with the Globus testing framework.
  • Tested with Java SE 6 (Beta 2).
  • Added two new usage statistics reported by Java WS Core: container uptime and a list of activated services.

To view the bug fixes, click here.

7.1.2. C WS Core

C WS Core implemented a security fix (by improving /tmp file handling for C WS Core tests) and a bug fix since GT 4.0.2.

To view the bug fixes, click here.

7.1.3. Python WS Core

Other than bug fixes, the only change that has occurred for Python WS Core since 4.0.2 is the fixing of a potential proxy generation race condition bug in "pyGsi", similar to the one in the Globus Toolkit

To view the bug fixes, click here.

7.2. Security

7.2.1. Message/Transport-level Security

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

To view the bug fixes, click here.

7.2.2. Pre-WS Authentication & Authorization

No changes have been made for Pre-Web Services Authorization & Authentication except for various bug fixes.

To view the bug fixes, click here.

7.2.3. MyProxy

The following changes have occurred for MyProxy since GT 4.0.2:

  • Updated GPT package from 3.5 to 3.6.
  • Added support for credential renewal via the MyProxy CA using myproxy-server.config authorized_renewers/default_renewers options
  • Provided an access control list for storing credentials via the myproxy-server.config accepted_credentials_mapfile option
  • Added support for VOMS attributes in myproxy-server.config policies
  • Changed MyProxy CA toissue certificates valid starting 5 minutes in the past to account for possible clock skew between hosts
  • Added check_multiple_credentials option in myproxy-server.config to allow clients to retrieve a credential for a given username even if the associated "credential name" isn't provided (via myproxy-logon --credname)

To view the bug fixes, click here.

7.3. Data Management

7.3.1. Reliable File Transfer (RFT)

The only changes for RFT since GT 4.0.2 are bug fixes.

To view the bug fixes, click here.

7.3.2. GridFTP

No changes have been made for GridFTP since 4.0.2. However, please remember that a protocol change was made in 4.0.1 to match a wuftpd extension regarding listings and resolve 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.

7.3.3. Replica Location Service (RLS)

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

To view the bug fixes, click here.

7.4. Information Services

7.4.1. WS MDS Aggregator Framework

Except for a bug fix, no changes have been made to the WS MDS Aggregator component since 4.0.2.

To view the bug fix, click here.

7.4.2. Pre-WS MDS

The only change for Pre-WS MDS since 4.0.2 was a bug fix.

To view the bug fix, click here.

7.5. Execution Management

7.5.1. WS GRAM

The following changes were made to WS GRAM since GT 4.0.2:

  • The MEJS now caches the user home directory values.
  • Error reporting for multijobs was improved.
  • Run queue threads now have more unique name (helps with debugging thread issues).

To view the bug fixes, click here.

7.5.2. Pre-WS GRAM

Pre-WS GRAM has performed a security fix and a bug fix since GT 4.0.2.

To view the bug fix, click here.

7.6. Cross-component Tools

7.6.1. CoG jglobus

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

  • Fixed handling of SSLv23 hello messages.
  • Optimized way of getting a default credential in GlobusGSSManagerImpl.
  • Increased the default transfer timeout in the GridFTP library to 30 seconds for FTP transfers and 60 seconds for GridFTP transfers.
  • Fixed potential security hole to ensure that files that are opened to write are created securely. Added createFile() method in the org.globus.util.Util class to do relevant checks. Also, ensured that appropriate permissions are set on created files before a write is done.

To view the bug fixes, click here.

8. All Fixed Bugs Since 4.0.2

8.1. Common Runtime Components

8.1.1. Java WS Core

The following bugs were fixed for Java WS Core:

  • Bug 4204: WorkManagerImpl incorrectly implements the WorkManager.schedule(...) method
  • Bug 4595: wsrf-query with a bad XPath query returns "null"
  • Bug 4325: Exceptions of type 'expectedType' could be more useful
  • Bug 4324: ServiceContainer reports failed startup at incorrect severity
  • Bug 4540: and Math example service error

8.1.2. C WS Core

The following bugs have been fixed in the C WS Core since GT 4.0.2:

  • Bug 4647: Improved /tmp file handling for C WS Core tests
  • Bug 4536: Fix error message in ws-addressing implementation

8.1.3. Python WS Core

Many bugs have been fixed for Python WS Core in the ZSI SOAP layer since 4.0.2. Check out the ZSI bug tracker on SourceForge.

8.2. Security

8.2.1. Message/Transport-level Security

The following bugs have been fixed for Message/Transport-level security since GT 4.0.2:

  • Bug 4647: Insecure temporary file handling in the Globus Toolkit
  • Bug 4648: grid-proxy-init proxy credentials race condition

8.2.2. Pre-WS Authentication & Authorization

The following bugs have been fixed for Pre-WS Authentication & Authorization since 4.0.2:

  • Bug 3484: grid-proxy-destroy destroys proxy even with -dryrun option, when specified with -all
  • Bug 3934: grid-proxy-init -pwstdin reads too many characters
  • Bug 4404: anonymous authentication with self authorization GSI
  • Bug 4505: grid-proxy-init should exit(0) on warning
  • Bug 4626: Typo in globus_error_openssl.c
  • Bug 4634: grid-proxy-init hangs when the proxy file already exists as a pipe
  • Bug 4554: Delegation error using under-developement globusrun-ws when I supply IP address and not DNS name
  • Bug 4648: grid-proxy-init proxy credentials race condition

8.2.3. MyProxy

The following bugs have been fixed for MyProxy since GT 4.0.2:

  • Bug 4647: Fixed insecure temporary file handling in myproxy-admin-adduser.
  • Fixed insecure input handling in myproxy-get-delegation.cgi example.

8.3. Data Management

8.3.1. Reliable File Transfer (RFT)

The following bugs have been fixed for RFT since GT 4.0.2:

  • Bug 4366: Bad 4.0.2 tag in ws-transfer?
  • Bug 4503: Incomplete file list
  • Bug 4643: race condition for requests with 2 directory creation
  • Bug 4639: globus_4_0_2 tag, java-only installation

8.3.2. Replica Location Service (RLS)

The following bugs have been fixed for RLS since GT 4.0.2:

  • Bug 3215: RLS client portability improvements
  • Bug 3830: RLS searches for RLI tables in LRC database
  • Bug 4647: Insecure temporary file handling in the Globus Toolkit

8.4. Information Services

8.4.1. WS MDS Aggregator

The following bugs were fixed for WS MDS Aggregator since GT 4.0.2:

  • Bug 4655: EntrySweeper should be a daemon thread

8.4.2. Pre-WS MDS

The following bug has been fixed for Pre-WS MDS since 4.0.2:

  • Bug 4663: gt4.0.2-all-source-installer with target prewsmds doesn't work with some compilers

8.5. Execution Management

8.5.1. WS GRAM

The following bugs have been fixed for WS GRAM since GT 4.0.2:

  • Bug 4376: Multijob shouldn't be distributing credential endpoints to subjobs
  • Bug 4577: GramJob not receiving notifications

8.5.2. Pre-WS GRAM

The following bug has been fixed for Pre-WS GRAM since GT 4.0.2:

8.6. Cross-component Tools

8.6.1. CoG jglobus

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

  • Bug 4414: clarify lifetime parameter in myproxy docs
  • Bug 4568: UserNamePrincipal is not serializable
  • Bug 4558: ws failure on corrupt grid-mapfile

9. Known Problems As of 4.0.3

9.1. Common Runtime Components

9.1.1. Java WS Core

The following problems and limitations are known to exist for Java WS Core at the time of the 4.0.3 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
    • Bug 4432: SimpleTopic.notify(SOAPElement element) drop child elements
    • Bug 4566: globus-deploy-gar insists that ANT_HOME be set

9.1.2. C WS Core

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

  • 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
  • The service engine and clients are not thread-safe

9.1.3. XIO

The following problems are known to exist for XIO at the time of the 4.0.4 release:

  • Bug 3082: Under certain circumstances there is a small memory leak.

9.1.4. C Common Libraries

The following problems are known to exist for C Common Libraries at the time of the 4.0.3 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 3171: add RFC 2253 principal name to JAAS subject?
  • Bug 3436: globus_uuid MAC address retrieval doesn't work on solaris
  • Bug 3581: gpt/globus_core improvements
  • Bug 3610: globus-makefile-header returns bad field
  • Bug 4035: MacOS threading issues
  • Bug 4097: Signal handling probrem on MacOS X
  • Bug 4318: Pkgdata needs to make source dir explicit

9.2. Security

9.2.1. Community Authorization Service (CAS)

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

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

9.2.2. MyProxy

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

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

9.3. Data Management

9.3.1. Reliable File Transfer (RFT)

The following problems are known to exist for RFT at the time of 4.0.3 release:

  • Bug 3121: Bug in enforcing maximum active transfers in a container

9.3.2. GridFTP

The following problems are known to exist for GridFTP at the time of the 4.0.3 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 3622: gridftp server improperly handles detach option in config file
  • Bug 3761: globus_ftp_control library hangs at various places (depending on os)
  • Bug 3807: "not a plain file" could be "file not found"
  • Bug 3845: data channel authentication failure
  • Bug 4119: Malformed UTF-8 character problem in globus-ftp-client tests
  • Bug 4274: client library has no default striping layout.
  • Bug 4344: Globus-url-copy client does not reuse the connection when run in 3rd party mode

9.3.3. Replica Location Service (RLS)

The following problems are known to exist for RLS at the time of the 4.0.3 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 3253: GT4 build fails on Mac OS X 10.4 Tiger
  • Bug 3656: ACLs cannot be modified dynamically
  • Bug 3828: RLSClient crashes when a null parameter is passed to a method
  • Bug 4114: Java apis fail on 64 bit machine (patch available)
  • Bug 4141: regexec call in auth.c's auth_getperms
  • Bug 4142: globus-rls-admin -s always indicates RLI does not exist
  • Bug 4512: RLS query returns incomplete result on 64bit system (patch available)
  • Bug 4630: RLS java client cannot load libaries through JNI on Mac (see workaround)
  • Bug 4654: Client core dumps when doing bulk attribute add (patch available)


The following problems are known to exist for OGSA-DAI at the time of the 4.0.3 release and will be addressed in the future. If you have any others that you feel should be added to this list then please let us know. You may also want to consult the platform-specific FAQ and general FAQ. Additional information may be posted in the advisories page which report any problems since the release, or the OGSA-DAI bugzilla which may also have information on any problems with the current release.

  • Performance:

    • Accessing the databaseSchema property for DB2/Cloudscape can sometimes retrieve unrelated meta-data and also cause OGSA-DAI to crash.
    • Accessing the databaseSchema property for Oracle causes a server-side java.lang.OutOfMemoryError.
    • Attempting to return a very large data set in a Response document can cause a server-side java.lang.OutOfMemoryError. This can be avoided by submitting an asynchronous request (one that uses an outputStream) and retrieving the results using a data service's data transport operations.
    • Queries of tables for millions of small rows can eventually cause a server-side java.lang.OutOfMemoryError even if using stream activities and data transport operations.
    • The fileWritingActivity attempts to read the whole file in a oner and so could cause a server-side java.lang.OutOfMemoryError for very large files.
    • Some databases, such as dBASE IV database on Microsoft Windows 2000, allow unusual characters, such as 0xC to be contained in certain field types. When field values containing this character, OGSA-DAI encodes them into invalid XML that subsequently causes Xerces-dependent components to raise an org.xml.sax.SAXParseException. Activities that have two outputs can sometimes cause java.lang.OutOfMemoryErrors to occur server-side if manipulating large amounts of data. This can arise when using the GZIP activities for example.

      • Such activities are driven by one of the two connected activities and the other activity can accumulate data without processing it. So, for example for the GZIP activities OGSA-DAI focuses on the GZIP meta-data output steam and data only flows from this stream when a file has been completely unzipped. Therefore for large files the whole contents of the file flows into the activity and is buffered without being sent on.
      • OGSA-DAI's GZIP activities will warn if memory usage is close to maximum and throw an OGSA-DAI exception server-side so that the web services container does not crash.
  • Error and exception handling:

    • The failure of a single activity in a request can cause the status of all activities to be set to ERROR, even those that are not connected and succeeded.
    • The data transport activities can gulp exceptions. For example if an sqlQueryStatement with a incorrectly formed SQL query statment is connected to an outputStream activity then attempting to pull data from the outputStream using the data transport operations results in no data - no indication of an error is given to the client.
    • The methods can sometimes log the wrong line numbers. Searching the logs will usually reveal where the problem actually arose.
  • Security:

    • Encrypted role map files are currently unsupported.
    • If a client does not provide a certificate then deliverFromGridFTP and deliverToGridFTP in a request will fail.
  • File activities:

    • The fileAccessActivity encodes text line-by-line if Base 64 encoding is being used. This may give different results from encoding a whole file in a oner.
    • In fileWritingActivity, EOF means "end of file" when perLine has value false but "end of line" when perLine has value true.
    • In fileWritingActivity only strings from its input stream are handled. Other block types e.g. bytes are ignored.
  • General:

    • Note that when deploying new data service resources dynamically via configurable data service this only works if the JARs required by the data service resource (e.g. database driver JARs) are already within the web service container's library directories. If this is not the case then the container has to be restarted.
    • The data service terminate operation currently does nothing. It is intended as a placeholder for future development.
    • Meta-data from a database, returned in the databaseSchema property, can be case-sensitive depending upon the database. For example MySQL might return a table called littleblackbook while DB2 returns LITTLEBLACKBOOK.
    • The class contains unimplemented methods which throw java.lang UnsupportedMethodException.
    • Conversion of java.sql.ResultSet to XML WebRowSet returns empty key-column and map properties in the properties element.
    • deliverFromGridFTP and deliverToGridFTP do not allow the setting of certain GridFTP parameters.
  • There is no support in the client toolkit for certain activities. These include:

    • directoryAccessActivity
    • fileAccessActivity
    • fileManipulationActivity
    • deliverFromFTP
    • deliverToFTP
    • gzipDecompression
  • The deliverToStream activity only works if services are deployed in Tomcat.

9.3.5. Data Replication Service (DRS)

The following problems are known to exist for DRS at the time of the 4.0.3 release.

  • See Java WS Core buglist concerning container freeze, which may affect DRS performance: Bug 3502: Container freezes (CPU spin) when making remote call between ws-resources. See record for WORKAROUND.
  • Bug 4231: DRS does not implement subscription/notification

9.4. Information Services

9.4.1. Web MDS

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

9.5. Execution Management

9.5.1. WS GRAM

The following problems are known to exist for WS GRAM at the time of the 4.0.3 release:

  • Bug 2734:non-shared FS scheduler file list
  • Bug 3675:wsrf gram client file streaming error
  • Bug 3726:GlobusRun error message typo
  • Bug 2974:Inconsistent Arguments
  • Bug 4356:globusrun-ws is overriding manual subjob credential deleg...
  • Bug 4513:LD_LIBRARY_PATH should not be set if no library_path is s...
  • Bug 4584:security descriptor uses operation field name instead of ...
  • Bug 2527:Add a failure case for non-existant queue to scheduler te...
  • Bug 2623:service summary/diagnostics
  • Bug 2680:Can't change source url for gram job staged files
  • Bug 2776:add directive to set the priority in the job description ...
  • Bug 3801:condor commands need CONDOR_CONFIG
  • Bug 3829:Separating the factory type from the resource name
  • Bug 3865:Enhance RSL with Job Name
  • Bug 3866:Support for parametric or array job types
  • Bug 3876:Automatic transfer of all files modified by a job in GRAM
  • Bug 3948:Service must release all of its resources on deactivation
  • Bug 4009:Use pbsdsh if available
  • Bug 4153:gram scheduler test failing - submit202
  • Bug 4191:globusrun-ws job submission hangs
  • Bug 4216:Empty submit_test/submitxxx.err causes FAILure in Local t...
  • Bug 4275:globus-gram-local-proxy-tool fails on Solaris
  • Bug 4452:job submission response is effected by java 1.5 thread pr...
  • Bug 4461:Configuring GRAM RM interface to use SSH or RSH
  • Bug bug
  • Bug 4539:Add script error #21 troubleshooting information.
  • Bug 4560:Changing default ports with ManagedJobFactoryClientHelper
  • Bug 4661:Example submit job
  • Bug 3638:Missing SEG developer documentation
  • Bug 4118:Rendezvous Documentation Needs Improvement
  • Bug 3672:Streaming with PBS fails
  • Bug 3242:Software selection thru WS GRAM RSL
  • Bug 2250:delegation required resource property
  • Bug 2578:reliable state change notification
  • Bug 2579:reliable state change notification
  • Bug 2624:Multiple job hold states and parameterized release operation
  • Bug 3088:Default Job Environment
  • Bug 3384:Inconsistent jobType/count parameter semantics
  • Bug 3460:State Mask for Notifications
  • Bug 3480:Allow usage of ssh to start SEG
  • Bug 3529:setup/postinstall fatal errors should be warnings
  • Bug 3569:Selectable jobType default per factory
  • Bug 3575:SEG dependent on GLOBUS_LOCATION env var
  • Bug 3714:Add Job elements to GLUECE RP
  • Bug 3741:pluggable job proxy creation
  • Bug 3748:WS-GRAM Plugable Resource Manager Backend
  • Bug 3751:convert persistence data store from files to a database
  • Bug 3803:Default scratchDirectory doesn't exist
  • Bug 3897:Must modify Globus in order to use authorization callouts
  • Bug 4178:no job output when streaming with globusrun-ws
  • Bug 4207:Enabling dynamic job description variables using softenv
  • Bug 4410:GT4 WS-GRAM Auditing
  • Bug 4431:freeze by Unsubmitted on personal WS GRAM
  • Bug 4474:globus-gridmap-and-execute problem with additional PDPs
  • Bug 4515:throughput tester - gram errors for cvs HEAD
  • Bug 4528:WS-GRAM Auditing Test Integration on TeraGrid
  • Bug 4545:WS GRAM JSDL Support in GT 4.2
  • Bug 4550:Multijob code not checking for existence of job credential
  • Bug 3126:RFT resource reference property TransferKey is poorly named
  • Bug 2980:Troubleshooting globusrun-ws

9.5.2. Pre-WS GRAM

The following problems are known to exist for Pre-WS GRAM at the time of the 4.0.3 release:

  • Bug 1037: globus-gram-reporter does not publish additional LSF job ...
  • Bug 1551: Race condition in job manager
  • Bug 1550: Fixes for race condition in job manager
  • Bug 1868: globus_gram_reporter is missing from GT 3.2.1 PreWS distr...
  • Bug 1934: Gatekeeper's syslog output cannot be controlled
  • Bug 2235: GT3.2.1 globus_gram_client_tools-4.3 patch broken
  • Bug 3373: globus removes the temporary job directory before pbs wri...
  • Bug 3425: personal gatekeeper does not work on AIX
  • Bug 3428: globus-personal-gatekeeper -list failing
  • Bug2739: Gatekeeper AuthZ/Gridmap Callout result logging
  • Bug 2741: catching SIGSEGV if dynamic loading of authorization modu...
  • Bug 4150: do not use break in Perl, use last
  • Bug 4235: globus-job-manager doesn't exit if the job fails.
  • Bug 4335: Incorrectly terminated message in globus-gram-job-manager...

9.5.3. Workplace Management Service (WMS)

The only known problem for Workspace Service Management (WMS) as of 4.0.3, is the following:

  • The LeasedAccountsResource implementation will quarantine an account if the expiration script fails for any reason; but currently we provide no user friendly mechanism for manually un-quarantining the account when the situation is cleared by an administrator. We are planning to release an update shortly.

9.6. Cross-component Tools

9.6.1. CoG jglobus

The following problems are known to exist for JGlobus module of the Java CoG Kit at the time of the 4.0.3 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