Status: New
Owner: vladimir.ralev
Labels: Component-Sip-Servlets Type-Enhancement MSS-1.5.0.FINAL
Release-Type-Alpha Roadmap-Fix Priority-Medium
New issue 2093 by vladimir.ralev: Session timers get mixed up when no
request affinity is enable in cluster
http://code.google.com/p/mobicents/issues/detail?id=2093
If requests from the same app session hit different nodes the SAS timer is
started on both nodes, we need only one node to run the timer. Same with
servlet timers. We must also invalidate sessions only on one node,
otherwise the JBoss Cache items are removed twice leading to deadlock and
session invalidation callbacks are called twice (once on each node.
NOTE: THis issue only affects JBCP 1.2.x and JBoss 4.x. In AS 5 and JBCP 5
the timer implementation is fault tolerant.
This case is linked to
https://c.na7.visual.force.com/apex/Case_View?id=500A0000004SxHI&sfdc.override=1
