This repository has been archived by the owner. It is now read-only.

@shorea shorea released this Aug 30, 2016 · 3 commits to master since this release

Assets 3

Support for Tomcat 8.5. Due to compatibility issues this release drops support for Tomcat 7.

See Issue #42

@shorea shorea released this Sep 25, 2015 · 9 commits to master since this release

Assets 3

Removing legacy code supporting transition between 1.x versions and 2.0.0. If you are still using a 1.x version you should not upgrade to this version without first upgrading to 2.0.0.

Addressing concerns in Issue #29 and Issue #30. New configuration option to delete corrupt sessions from the database. https://bz.apache.org/bugzilla/show_bug.cgi?id=58284 is related to this release.

@shorea shorea released this Apr 2, 2015

Assets 3

Merges @Selindek changes in Pull Request #19 to fix a bug where stale sessions stored in DynamoDB were incorrectly overwriting active sessions in memory. Existing users (using v1.0.4 or below) should first deploy v1.0.5 before upgrading to this release. More detailed migration notes are included in the release notes for v1.0.5.

Assets 3

This release is meant only as an intermediate hop to version 2.0. New users of Amazon DynamoDB Session Manager for Apache Tomcat should use version 2.0 or above as 1.x versions have a serious bug regarding stale session data ( See Pull Request #19 ).

Migration Notes

To migrate successfully from a 1.x version to 2.0 please follow these instructions. Migrating directly to version 2.0.0 from version 1.0.4 or below could cause session data loss or corruption.

  1. Deploy v1.0.5 to all servers in your cluster. When the deployment is complete all servers will now be able to parse the new record format in DynamoDB but will continue to write in the 1.x record format.
  2. Deploy v2.0.0 to all servers in your cluster. This release will start writing in the new record format but can still understand the 1.x record format so over time your session records will be converted to the new schema.

It's important to ensure that all deployments complete successfully and Tomcat is restarted on each server.

@shorea shorea released this Mar 11, 2015 · 16 commits to master since this release

Assets 3

This release includes the following changes:

  • #17 Tomcat 8 support
  • Update the AWS Java SDK to the latest version

@hanshuo-aws hanshuo-aws released this Jan 29, 2015 · 27 commits to master since this release

Assets 3

This release includes the following changes:

  • #12 Add support for proxy configuration
  • #14 Fix the issue that maxInactiveInterval was incorrectly treated as milliseconds when passed into ExpiredSessionReaper.
  • #16 Update the AWS Java SDK (now it supports eu-central-1 region)
  • Update maven compiler to Java 1.6
Assets 3

This release resolves an issue where the incorrect class loader was being used when deserializing objects. This prevented the session manager from being able to store custom objects.

For more information on using the session manager, see the AWS SDK for Java Developer Guide.

Assets 3

We're excited to announce a new open-source project built on top of the AWS SDK for Java.

The Amazon DynamoDB Session Manager for Apache Tomcat enables you to easily store session data from your Tomcat web applications in Amazon DynamoDB.

This first release of the session manager supports the basic operations for loading and saving session data in Amazon DynamoDB. Some features are not available yet, such as session locking. If there's a feature you need, let us know, either with an issue, or even better... with a pull request!

For more information on using the session manager, see the AWS SDK for Java Developer Guide.