A bit about the setup I'm using:
1 haproxy as a load balancer'
2 tomcat6 nodes;
2 memcached nodes;
Non-sticky mode. Kryo serialization strategy;
Operation and sessionBackup timeouts are default;
Locking startegy: auto.
What steps will reproduce the problem?
1. Start all the nodes
2. Login into application
3. Check that session backup is saved in the secondary memcached nodes
4. Shutdown the primary memcached node
5. Navigate to some other page in application (sometimes I get dropped to log
in screen with new session identifier not sure why this is happening but it's
possibly caused by timeouts)
6. Restore the memcached node (it takes a while for tomcat to detect that node
is back to up state and store the backup of session into it. I'm looking for
the options to change this timeout)
7. As the session backup process is triggered by user requests, in this step
I'm making some interactions with the application until the session is stored
as backup.
8. Kill other node (which is now primary)
9. Next interation with application will get me into the login screen (session
information lost), but if I'll change the session id to the session that had to
be restored then I will be able to use application with that session
identifier).
Basically it's quite interesting situation and currently I'm not sure what
causing this behaviour as I can't stabily reproduce this issue. Any suggestions
will be appreciated.
Original issue reported on code.google.com by d3da...@gmail.com on 24 Jun 2015 at 1:46
Original issue reported on code.google.com by
d3da...@gmail.comon 24 Jun 2015 at 1:46