Issue Details (XML | Word | Printable)

Key: GLASSFISH-16615
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Mahesh Kannan
Reporter: Shing Wai Chan
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

HA session expires issue

Created: 11/May/11 04:50 PM   Updated: 17/Oct/11 04:54 PM
Component/s: failover
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Status Whiteboard:

3_1-next

Tags: 3_1-next 3_1_1-scrubbed 3_1_x-exclude
Participants: Mahesh Kannan and Shing Wai Chan


 Description  « Hide

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.



Shing Wai Chan added a comment - 11/May/11 04:56 PM

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.


Mahesh Kannan added a comment - 20/May/11 04:54 PM

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