Globus Toolkit® 3.2 RLS Release Notes

The Replica Location Service (RLS) is a Pre-WS component that maintains and provides access to mapping information from logical names for data items to target names.

The 3.2 release contains bug fixes and extended functionality. In particular, this version of RLS supports the deployment of a hierarchy of Replica Location Index (RLI) nodes.

Note: The version numbers below refer to RFT versions.

2.2

  • Memory leak fix when LRC or RLI updating an RLI that's down for extended periods.
  • Args reversed when limiting results when not using MySQL.
  • Fix typo in SQL that retrieves attribute values.

2.1.4

  • Fix for RLI initialization code

2.1.3

  • Fix valuge_get_bulk, RLSStats in java API

2.1.2

  • Added support for Oracle

2.1.1

  • Fix race condition in RLI-RLI updates that could corrupt DB

2.1.0

  • Add support for RLI to RLI updates
  • Clean up dependencies in server-setup package

2.0.9

  • Add bulk operations to RPC doc

2.0.8

  • Add bulk attribute operations
  • Server will now start up successfully even if DBMS cannot be connected to
  • Fix table counters, could get off if a transaction was rolled back

2.0.7

  • Tested with GT3
  • Configuration option to specify RPC timeout for RLS server/server operations

2.0.6

  • Fix race condition leading to server not accepting new connections

2.0.5

  • Buffer output to minimize packets during bulk operations

2.0.4

  • Support for bulk update and query operations
  • Fix signal handler to avoid calls to pthread_cond_signal (can lead to hung thread on linux)
  • Fix date parsing problem when using Postgres

2.0.3

  • Support for Postgres as well as MySQL

2.0.2

  • Fix config file parsing problem (handle extraneous whitespace better)

2.0.1

  • Fix RLI "exists" functions when using Bloom filters
  • Fix globus_rls_client_attr_value_get() when attribute specified by name
  • Return error when globus_rls_client_attr_modify() finds no attributes to modify

2.0.0

  • Query operations now fully support limits on the number of results, on both client and server side
  • Fix for handling string attribute value that's an empty string