Comment #14 on issue 1974 by jean.deruelle: [MSS HA] When app call
setExpires, it is not propagated to the failover node
http://code.google.com/p/mobicents/issues/detail?id=1974
This issue was updated by revision r16930.
Committing another Fix against JBCP 1.2.X branch.
This fix the issue where if we restart the other engine instead of just
shutting it down the other node is loading the session and marking it as
dirty causing the other node to refresh it again (wondering if this could
cause a deadly embrace leading ultimately to the writelocktiemout we were
seeing)