Status: Accepted
Owner: [email protected]
Labels: Type-Defect Priority-Medium
New issue 2314 by [email protected]: Active MSS nodes that is not aware
of remote node activity will expire the app session
http://code.google.com/p/mobicents/issues/detail?id=2314
When two nodes were hot with requests for the same app session if only one
the nodes is serving requests the SAS timer will expire on the idle node
which in turn will proceed with the remote invalidation resulting in a lost
call.
The reason for this issue is that the idle node only receives the
serialized data without parsing it and updating the locally loaded app
session. This works perfect when there is affinity and allows memory
efficiency, but if there is no affinity leads to number of errors.
The fix for this issue would be to refresh the session every time we
receive SAS node modification notification.
Linked to
https://c.na7.visual.force.com/apex/Case_View?id=500A0000006Gi5G&sfdc.override=1
Additional problem found is that there seem to be two notification instead
of one (look for "Refreshing")
Attachments:
idle-expiration-issue-logs.txt 32.2 KB