-
Type:
Bug
-
Status: Closed
-
Priority:
Normal
-
Resolution: Fixed
-
Affects Version/s: 3.1.1
-
Fix Version/s: 3.1.2
-
Component/s: None
-
Labels:
-
Similar issues:
-
Flagged:Flagged
-
Sprint:Tiger Sprint 118
Actually the catch of the publish/unpublish exception is followed by
log.error("Execution of scheduled workflow operation {} on {} failed", methodName, subjectPath, e);
Here, the last variable which is the actual exception is ignored. It would be nice to have the stacktrace logged as well
- is backported by
-
CMS-9728 Back port to 10.0: scheduled task doesn't log the stacktrace when an error occurs in publish/unpublish workflow calls
-
- Closed
-
- is forward ported by
-
REPO-1395 Forward port to 10.2/trunk, scheduled task doesn't log the stacktrace when an error occurs in publish/unpublish workflow calls
-
- Closed
-