Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.1.15
-
Fix Version/s: 6.1.16
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
The scavenging done in the TerracottaSessionManager is driven with a single threaded ScheduledExecutorService. Unfortunately it seems that if an exception occurs during scavenge() two bad things happen:
1) The exception is not reported anywhere
2) The fixed rate scavenge task is removed from scheduling so no more scavenging happens after that
This seems to be standard behavior for ScheduledExecutorService it seems but doesn't seem correct for the usage in the terracotta session manager.
As a point of comparsion, HashSessionManager catches all exceptions and logs a warning in scavenge()
Tim also separately posted a patch for some other niggles he found. I'm attaching it to this issue.
Jan