-
Bug
-
Resolution: Done
-
Major
-
7.0.0.CR1
-
None
-
User Experience
-
-
-
-
-
-
EAP 7.0.1
When ageout-history cannot delete the old CP files, it silently fails and returns "success".
LocalAgeoutHistoryHandler#recursiveDelete does keep track of whether the
delete failed or succeeded, but the return value from this method is ignored
in execute(...).
If recursiveDelete returns false, it should report a failure.
- clones
-
WFCORE-1525 ageout-history does not report failures
- Resolved
- is incorporated by
-
JBEAP-4637 Upgrade to WildFly Core 2.1.5
- Closed