Table of Contents

  1. Fedora 2.1 Release
  2. Performance Tuning
  3. Bug Fixes
  4. Known Issues
  5. Installation
  6. Historic Release Notes (prior releases)

The Fedora Project is proud to announce the release of version 2.1.1 of the Fedora open-source digital repository system. Fedora 2.1.1 is a maintenance release that provides a significant performance boost for Fedora 2.1. It also resolves a number of reported bugs.

  1. Fedora 2.1 Release

    If you are not already familiar with Fedora 2.1, please consult the Fedora 2.1 Release Notes before installing the new Fedora 2.1.1 maintenance release.

    Since Fedora 2.1.1 is a maintenance release, it contains all of the same features as Fedora 2.1. Please refer to the Fedora 2.1 documentation for a complete description of Fedora 2.1 and 2.1.1 functionality.Fedora 2.1 contains all of the standard Fedora features built around web services, XML, and RDF, as well as many new features such as the new Fedora security architecture, XACML-based policy enforcement, the Fedora Service Framework, the new OAI Provider service, the Repository Rebuilder, and many other new features and enhancements. Now, Fedora provides an even more powerful, flexible, and secure foundation for a wide variety information management applications, including institutional repositories, digital libraries, e-research, e-scholarship, records management, digital archives, and educational software.

  2. Performance Tuning

    With the addition of the Fedora 2.1.1 maintenance release, a Fedora repository will now perform each management operation within milliseconds per API-M SOAP request.

    In response to user feedback, a complete analysis of Fedora API-M performance was conducted which revealed bottlenecks on several operations, most notably modifyDatastreamByValue, purgeDisseminator, and purgeObject. The Fedora server has been significantly tuned so that these bottlenecks are eliminated. Please consult the final report which contains before/after performance measurements for every API-M operation.

    new item image Fedora API-M Performance Report

  3. Bug Fixes

    Refer to Fedora's Bugzilla for full descriptions of the resolved bugs.

    • Bug #145: FedoraClient's HTTP header date parsing fails in non-english locales
    • Bug #146: ResourceIndex Rebuilder error with relative path for triplestore
    • Bug #147: SQL database left in corrupted state after ingest of object with label exceeding 255 characters
    • Bug #148: Admin client bDef/bMech builders fail when specifying system generated PID
    • Bug #149: Adding sample policy results in NullPointerException
    • Bug #151: Surrogate policies generate errors in console log
    • Bug #152: Performance issue: modifyDatastreamByValue delay when Resource Index is ON
    • Bug #154: Resource Index datastore parameter, poolMaxGrowth, doesn't behave as documented
    • Bug #155: DirIngest not following redirect to SSL
    • Bug #156: Modifying a disseminator's bmech breaks disseminations for other objects
    • Bug #157: Deleting digital object leaves behind triples in Resource Index
    • Bug #158: Performance issue: purgeObject and purgeDisseminator take unreasonably long in large repositories
    • Bug #159: Error in sample policy (deny-objects-by-pids-to-tomcat-role.xml)
  4. Known Issues
    • An early adopter of Fedora 2.1 reported anomalous 401 status codes returned after a period of normal server use. This problem is difficult to replicate, and the cause is unknown. A workaround to this problem is to instruct Tomcat to use a MemoryRealm instead of a JAASRealm. See Bug 144 for detailed instructions on applying this workaround.
    • Ingest validation error when namespace for in-line XML datastreams is in root element. Reported as Bug 153.
    • fedora-reload-policies.sh gives usage error if run with no arguments. Reported as Bug 160.
    • MacOS X users must upgrade to Java 5. Reported as Bug 162.
  5. Installation

    For instructions on installing and upgrading Fedora, please consult the Installation Guide and the Upgrade and Migrate Guide.

    NOTE: In Fedora 2.1.1, the repository persistent storage layer (i.e., LowLevelStorage) has been refactored into a configurable module. This is to make it consistent with the overall Fedora repository design where each piece of functionality exists as a module in the Fedora server. Modules can easily be replaced with alternative implementations of the core functionality. For example, in the next release of Fedora will will ship two different LowLevelStore implementations: the existing file system implementation, and a Storage Resource Broker (SRB) implementation. If you are upgrading from a previous version of Fedora, you should note that all storage-related server configuration parameters now exist in the LowLevelStorage module section of the Fedora Configuration file (fedora.fcfg). Previously, these parameters were stand-alone parameters in the Fedora Configuration file. These parameters are: object_store_base, datastream_store_base, path_registry, path_algorithm, file_system, and backslash_is_escape.

    NOTE: In Fedora 2.1.1, the Resource Index is OFF by default. To turn it on, modify the Fedora Configuration file (fedora.fcfg) so that the Resource Index module is configured to level 1 or 2. (Default is level 0).

  6. Historic Release Notes

    Release notes for previous versions of Fedora: [2.1], [2.1b], [2.0], [1.2.1], [1.2], [1.1.1], [1.1], [1.0], [0.9], [Beta 1], [Alpha 1]