[GLASSFISH-16615] HA session expires issue Created: 11/May/11  Updated: 17/Oct/11

Status: Open
Project: glassfish
Component/s: failover
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Shing Wai Chan Assignee: Mahesh Kannan
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Status Whiteboard:


Tags: 3_1-next, 3_1_1-scrubbed, 3_1_x-exclude


Suppose we have a load balancer with 3 instances.
1. A section, s1, is created in instance 1 for a given app.
2. There is a network issue. instance 1 is not available in the network.
3. Subsequent requests go to instance 2.
4. The session, s1, in instance 1 is still in memory and will be expired, and then removed.
This will cause an issue.

The same issue is in HA SSO.

Comment by Shing Wai Chan [ 11/May/11 ]

In case of HA SSO, one also need versioning in order to solve the problem. This has been filed as issue GLASSFISH-16377 and the fixed has been checkin to trunk.

Comment by Mahesh Kannan [ 20/May/11 ]

This really requires a new feature to be implemented in shoal. Basically, it requires shoal to maintain info about which instance is the owning instance of a session. This allows shoal to ignore stale 'remove-expire" commands.

This is a new feature and hence deferring it to 3.1-next

Generated at Sun Oct 23 16:36:16 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.