Too many *WARN* in the log , when the the url is malformed | Community
Skip to main content
yuriiv54804449
yuriiv54804449
Level 2
March 25, 2016
Solved

Too many *WARN* in the log , when the the url is malformed

  • March 25, 2016
  • 1 reply
  • 841 views

Hi All,

In case one is hitting a malformed url we get a lot of WARN messages in the log. 

For instance, if I enter http://localhost:4503/content/geometrixx/en.html?p=|   (the last symbol is pipe) it's handled correctly but  I can see 19 WARN messages in the logs (attached)

What I can do about it to suppress those annoying messages in the log? or even have only 1 WARN message

Thanks in advance,

Yura. 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by kautuk_sahni

    Hi

    Please have a look at this community article:

    Link:-http://cq-ops.tumblr.com/post/78113074496/how-to-suppress-informational-log-messages-from

    You can use the “Apache Sling Logging Logger Configuration” OSGi configuration at /system/console/configMgr to suppress a message such as follows:

    28.02.2014 01:55:05.596 *INFO* [Thread-1078954] com.corporation.generics.services.services.impl.GsaServiceImpl >>>>>> Entering the buildUrl method

    1) Raise the “Log Level” threshold one step higher (from INFO to WARN)

    2) In the “Logger” field, enter the name of the package causing trouble (com.corporation.generics.services.services.impl.GsaServiceImpl)

    See below:

    image

    It takes effect immediately on saving - no re-start necessary.

     

    Apache Sling Logging Configuration

    Configure:

    • Log Level and Log File, to define the location and log level of the central logging configuration (error.log). The level can be set to one of DEBUG, INFO, WARN, ERROR and FATAL.
    • Number of Log Files and Log File Threshold to define the size and version rotation of the log file.
    • Message Pattern defines the format of the log messages.

    For further information see AEM Logging and Sling Logging.

     

    I hope this would help you.

     

    Thanks and Regards

    Kautuk Sahni

    1 reply

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity ManagerAccepted solution
    Community Manager
    March 28, 2016

    Hi

    Please have a look at this community article:

    Link:-http://cq-ops.tumblr.com/post/78113074496/how-to-suppress-informational-log-messages-from

    You can use the “Apache Sling Logging Logger Configuration” OSGi configuration at /system/console/configMgr to suppress a message such as follows:

    28.02.2014 01:55:05.596 *INFO* [Thread-1078954] com.corporation.generics.services.services.impl.GsaServiceImpl >>>>>> Entering the buildUrl method

    1) Raise the “Log Level” threshold one step higher (from INFO to WARN)

    2) In the “Logger” field, enter the name of the package causing trouble (com.corporation.generics.services.services.impl.GsaServiceImpl)

    See below:

    image

    It takes effect immediately on saving - no re-start necessary.

     

    Apache Sling Logging Configuration

    Configure:

    • Log Level and Log File, to define the location and log level of the central logging configuration (error.log). The level can be set to one of DEBUG, INFO, WARN, ERROR and FATAL.
    • Number of Log Files and Log File Threshold to define the size and version rotation of the log file.
    • Message Pattern defines the format of the log messages.

    For further information see AEM Logging and Sling Logging.

     

    I hope this would help you.

     

    Thanks and Regards

    Kautuk Sahni

    Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...