Details
-
Bug
-
Resolution: Done
-
Major
-
7.2.2.GA
Description
Currently, the expiration of a given SFSB is scheduled for the current time + the @StatefulTimeout duration. However, a topology change cause a change in ownership, expiration for newly owned SFSBs are scheduled on the local member. Because these are not scheduled using the last accessed time, it is possible that regular topology changes can defer SFSBs from expiring indefinitely.
This can cause a memory leak
Attachments
Issue Links
- clones
-
WFLY-12401 Timely topology changes can defer expiration of distributed SFSB
- Closed