Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
3.1.1
-
None
-
Flagged
-
Tiger Sprint 118
Description
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
Attachments
Issue Links
- 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