Uploaded image for project: 'ActiveMQ Apollo (Retired)'
  1. ActiveMQ Apollo (Retired)
  2. APLO-248

Log stack traces to a separate log file by default.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.5
    • apollo-util
    • None

    Description

      Right now if an exception occurs in the broker, it's logged but not the stack trace. You would have to enable debug level logging to see that stack trace. So when users run into an exception and log an issue, they can't include the stack trace associated the exception which makes it harder to troubleshoot the problem.

      Attachments

        1. APLO-248.patch
          1 kB
          Hiram R. Chirino

        Activity

          People

            chirino Hiram R. Chirino
            chirino Hiram R. Chirino
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: