Service Virtualization

Expand all | Collapse all

Logs are not Updated

Jump to Best Answer
  • 1.  Logs are not Updated

    Posted 02-03-2020 03:51 AM
    Hi Team,

    We have set  log4j.rootCategory=ERROR,AR values in the logging.poroperties file but vse.logs, portal.logs, registry.logs are not updating and we are using devtest 10.2.4, Could you please let us know the reason

  • 2.  RE: Logs are not Updated

    Broadcom Employee
    Posted 02-03-2020 03:57 AM
    Hi Sai
              Please, would you mind posting the complete file content here. If you have a constraint to share, please just check if the Appender defined down below in the same document has been defined as AR. By default the appender name is A1.

    Sankar Natarajan

  • 3.  RE: Logs are not Updated

    Posted 02-03-2020 04:04 AM
    Thanks Sankar for quick response, I will update appender name as A1 and will check. I can not share the complete file content here, Could you please let me know what is A1 and what AR, how it will impact updating the logs?

  • 4.  RE: Logs are not Updated
    Best Answer

    Broadcom Employee
    Posted 02-03-2020 04:12 AM
    HI Sai
               In this entry below, the second parameter is the name of appender which is typically defined in the same document.


    Appender Definition:

    log4j.appender.A1.layout.ConversionPattern=%d{ISO8601}{UTC}Z (%d{HH:mm}) [%t] %-5p %-30c - %m%n

    You can give any name to the appender, but just make sure whatever name you have given to the appender in this entry, log4j.rootCategory=ERROR,AR, the same name AR is referred in the Appender definition like,

    log4j.appender.AR.layout.ConversionPattern=%d{ISO8601}{UTC}Z (%d{HH:mm}) [%t] %-5p %-30c - %m%n  

     Please check and make sure you referred the appender with the same name as it is defined with.
    Sankar Natarajan