Version 5x release notes

March 6, 2014 - June 25, 2015

 


Release 5.0.9 (01/16/2015: Upgrade dependency version of API Checker)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Known Issues

  1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS

Release 5.0.5 (09/22/2014: Bug fix for Translation Filter)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

 

New Features

  1. Set GenericBlockingResourcePool size to 100 max entries for all pools related to translation filter.   REP-1059 - Getting issue details... STATUS

Bug Fixes

  1. Made changes to translation filter so that we more intelligently handle the document cache only removing the items we add. REP-989 - Getting issue details... STATUS

Known Issues

  1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS

 

Release 5.0.4 (9/9/2014: Bug fix for Translation Filter)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Bug Fixes

  1. Translation filter memory leak resolved.  REP-929 - Getting issue details... STATUS
  2. Akka implementation causes status code 500 response under load.  REP-558 - Getting issue details... STATUS

Known Issues

  1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS

Release 5.0.2 (7/18/2014: Bug fix for Translation Filter)

Bug Fixes

  1. Translation filter was not behaving in a thread safe manner, it should now behave in a more thread safe manner.  REP-795 - Getting issue details... STATUS

Known Issues

  1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS

Release 5.0.0 (3/6/2014: Intra-filter Logging)

Key Summary T P Status Assignee
Loading...
Refresh

Breaking changes

  1. Removed Rackspace Auth 1.1 logic. The endpoint is gone, and so this wouldn't work anyway. However, now the configuration isn't valid any longer, so if you've got configuration that includes these settings, it must be removed.  REP-17 - Getting issue details... STATUS
  2. System Model Interrogator contract changed to use Optionals from the Guava library (to force handling of null pointers).
  3. The deprecated connection framework option has been removed. The -cf flag may no longer be used when launching Repose.  REP-562 - Getting issue details... STATUS

New features

  1. Added intrafilter logging of requests and responses at the trace level, including a UUID header.  REP-28 - Getting issue details... STATUS
    1. Intrafilter Logging allows Repose users to debug requests as they're passed through each filter. This allows users to easily diagnose and troubleshoot their configuration without ambiguity.

Bug fixes

  1. Loosened media type matching for translation to ignore media type parameters.  REP-206 - Getting issue details... STATUS
  2. Stopped returning 200 on certain internal errors, now we return 500 correctly.  REP-276 - Getting issue details... STATUS
  3. Resolved Null Pointer Exception when localhost is not a node in the system-model.cfg.xml.
  4. Resolved Null Pointer Exception when port-config element not present in dist-datastore.cfg.xml.  REP-7 - Getting issue details... STATUS
  5. Resolved Null Pointer Exception when Repose is started in a container without certain properties.  REP-234 - Getting issue details... STATUS
  6. Refactored utilities, including consolidation of some packages.  REP-280 - Getting issue details... STATUS

Known Issues

  1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS