{"action":"created","issue":{"url":"https://api.github.com/repos/aws/aws-dynamodb-session-tomcat/issues/41","repository_url":"https://api.github.com/repos/aws/aws-dynamodb-session-tomcat","labels_url":"https://api.github.com/repos/aws/aws-dynamodb-session-tomcat/issues/41/labels{/name}","comments_url":"https://api.github.com/repos/aws/aws-dynamodb-session-tomcat/issues/41/comments","events_url":"https://api.github.com/repos/aws/aws-dynamodb-session-tomcat/issues/41/events","html_url":"https://github.com/aws/aws-dynamodb-session-tomcat/issues/41","id":164974363,"number":41,"title":"Sticky Session Failover not working","user":{"login":"prowave","id":4467101,"avatar_url":"https://avatars.githubusercontent.com/u/4467101?v=3","gravatar_id":"","url":"https://api.github.com/users/prowave","html_url":"https://github.com/prowave","followers_url":"https://api.github.com/users/prowave/followers","following_url":"https://api.github.com/users/prowave/following{/other_user}","gists_url":"https://api.github.com/users/prowave/gists{/gist_id}","starred_url":"https://api.github.com/users/prowave/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/prowave/subscriptions","organizations_url":"https://api.github.com/users/prowave/orgs","repos_url":"https://api.github.com/users/prowave/repos","events_url":"https://api.github.com/users/prowave/events{/privacy}","received_events_url":"https://api.github.com/users/prowave/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-07-12T01:23:59Z","updated_at":"2016-08-26T06:45:44Z","closed_at":null,"body":"We opened a ticket with AWS support today and they asked us to open an issue here regarding the SessionManager with DynamoDB.\r\n\r\nThe AWS Engineer was able to reproduce this on his end as well.\r\n\r\nWe have an ElasticBeanstalk App running Java8, Tomcat8 and aws-dynamo-session-tomcat 2.0.0.  We are using this DynamoDB Session Manager, configured as you have specified in the documentation referenced in this project's README.md file.\r\n\r\nThe symptom is that when the application scales down, or we perform a rolling deployment or restart across the Beanstalk cluster; when a node drops and the end user is directed to a different node, the session state is not available on the new node.   This is what provides the Session Replication feature that allows cluster maintenance and scaling.  The user gets a new HttpSession and has to login again. \r\n\r\nAre you aware of this issue, and can you work with me to find a resolution?  \r\n\r\nThank you."},"comment":{"url":"https://api.github.com/repos/aws/aws-dynamodb-session-tomcat/issues/comments/242643964","html_url":"https://github.com/aws/aws-dynamodb-session-tomcat/issues/41#issuecomment-242643964","issue_url":"https://api.github.com/repos/aws/aws-dynamodb-session-tomcat/issues/41","id":242643964,"user":{"login":"kewlzero3","id":11522687,"avatar_url":"https://avatars.githubusercontent.com/u/11522687?v=3","gravatar_id":"","url":"https://api.github.com/users/kewlzero3","html_url":"https://github.com/kewlzero3","followers_url":"https://api.github.com/users/kewlzero3/followers","following_url":"https://api.github.com/users/kewlzero3/following{/other_user}","gists_url":"https://api.github.com/users/kewlzero3/gists{/gist_id}","starred_url":"https://api.github.com/users/kewlzero3/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kewlzero3/subscriptions","organizations_url":"https://api.github.com/users/kewlzero3/orgs","repos_url":"https://api.github.com/users/kewlzero3/repos","events_url":"https://api.github.com/users/kewlzero3/events{/privacy}","received_events_url":"https://api.github.com/users/kewlzero3/received_events","type":"User","site_admin":false},"created_at":"2016-08-26T06:45:44Z","updated_at":"2016-08-26T06:45:44Z","body":"I'll give the beta a try. Where can I download the beta jar?"}}
{"actor":{"display_login":"kewlzero3"}}