Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.2
    • Fix Version/s: 4.0_b83
    • Component/s: logging
    • Labels:
      None
    • Environment:

      Linux

      Description

      Steps to reproduce:

      • go to admin console (http://localhost:4848)
      • click on "server (Admin Server)"
      • click button "View Log Files"
      • in Log level combobox select WARNING
      • press Search button

      You still have INFO, SEVERE and WARNING messages in "Log Viewer Result" table. This happens on 3.1.2.2 too.
      Please not that there are two INFO levels in combobox "Log Level". I think this is wrong too.

        Activity

        Hide
        Anissa Lam added a comment -

        Thats a GUI issue.

        Show
        Anissa Lam added a comment - Thats a GUI issue.
        Hide
        Anissa Lam added a comment -

        Issues need to be addressed before 4.0 HCF (3/25)

        Show
        Anissa Lam added a comment - Issues need to be addressed before 4.0 HCF (3/25)
        Hide
        Anissa Lam added a comment -

        There is a bug in console that doesn't pass in the correct logLevel to the backend.
        I have just fixed that in rev. 60650. Please ensure you have the latest code.

        However, even with the fix, it seems the method getLogRecordsUsingQuery() still ignores it. eg, even specifying WARNING as the logLevel, it still returns all the INFO logs.

        Besides ignoring logLevel, I also see the problem when specifying 'listOfModules'. If this is specified, it will always return an empty list.

        Transfer to logging to take a look.

        Show
        Anissa Lam added a comment - There is a bug in console that doesn't pass in the correct logLevel to the backend. I have just fixed that in rev. 60650. Please ensure you have the latest code. However, even with the fix, it seems the method getLogRecordsUsingQuery() still ignores it. eg, even specifying WARNING as the logLevel, it still returns all the INFO logs. Besides ignoring logLevel, I also see the problem when specifying 'listOfModules'. If this is specified, it will always return an empty list. Transfer to logging to take a look.
        Hide
        sandeep.shrivastava added a comment -

        Committed revision 60932. This should take care of the Level filter, however the modulesList we are getting in the back end code is not as expected. We expect a java.util.List of the module names but we are getting a List object with a single entry which contains comma separated values with surrounding []. This needs further investigation.

        Show
        sandeep.shrivastava added a comment - Committed revision 60932. This should take care of the Level filter, however the modulesList we are getting in the back end code is not as expected. We expect a java.util.List of the module names but we are getting a List object with a single entry which contains comma separated values with surrounding []. This needs further investigation.
        Hide
        sandeep.shrivastava added a comment -

        This should be fixed by Jason Lee's recent fixes to the JSON marshaling code.

        Show
        sandeep.shrivastava added a comment - This should be fixed by Jason Lee's recent fixes to the JSON marshaling code.

          People

          • Assignee:
            sandeep.shrivastava
            Reporter:
            kovica
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: