Uploaded image for project: 'Zanata'
  1. Zanata
  2. ZNTA-1255

Enable DEBUG logging for Weld messages with string "Catching"

    Details

    • Type: Task
    • Status: Closed (View workflow)
    • Priority: unspecified
    • Resolution: Ready for Release
    • Affects Version/s: None
    • Fix Version/s: platform-4.0.0
    • Component/s: None
    • Labels:
      None
    • Tested Version/s:
      None
    • Sprint:
      16.20, 16.21, 16.22, 16.19
    • Story Points:
      0.5

      Description

      Weld sometimes logs error messages without stack traces, unless you enable DEBUG for the relevant category. (Sometimes even TRACE.) The stack traces are logged by methods in Weld like catchingDebug and catchingTrace, and they all seem to use the log message "Catching" together with message codes like PROBE-000000 or WELD-ENV-000000 (ie a 6 digit padded 0).

      In our test config (and our development config, eg docker/rundev.sh), we should enable filtered DEBUG logging for org.jboss.weld, so that "Catching" or "-000000" messages will get through. (Filtering by either one should be okay.)

        Attachments

          Issue links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. ZNTA-1256 ERROR log: WELD-000019 Error destroying an instance org.zanata.security.ZanataIdentity

          • unspecified - unspecified
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. ZNTA-1703 "Error destroying an instance" triggered by logout

          • Low - Minor problem or easily worked around.
          • Closed

            Activity

              People

              • Assignee:
                pahuang Patrick Huang
                Reporter:
                sflanigan Sean Flanigan
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: