Updates:
Labels: JBCP12-Patch-1.2.10
Comment #1 on 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
Also, for safety, we don't kill the timer ever. Both nodes will have the
timer started, because if one node dies it won't be notified to restart the
timer. So in this expiration case both nodes will call the expiration
callback independently. This case is handled gracefully in JBoss 5 only.
This problem doesnt affect JBoss 5 and cluster framework.
We could change that either way, but to avoid a leak in case of failure
before expiration, we can let it go like this.
