Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-2531

OperationTracker doesn't report path when failing to create exception report files

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.4
    • Fix Version/s: 5.4.1
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      Currently, if OperationTracker is blocked from creating its exception report file due to file permissions, the error message in the console doesn't give the path where it is trying to create the file:

      [ERROR] TapestryModule.ExceptionReporter Unable to write exception report exception-20160215-151536-801.0.txt: No such file or directory

        Attachments

          Activity

            People

            • Assignee:
              bobharner Bob Harner
              Reporter:
              bobharner Bob Harner
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: