Hello all,

When we enabled log4j.logger.TM1.Lock.CriticalSection=DEBUG in one of our instances. the server.log flooded with messages in the screenshot. The file reached 100 MB in couple of minutes and all messages are like this.

I will appreciated if you can help why it act like this while in the technote says "This particular logger is a low cost logger, that is OK to leave enabled at all times (inlcuding in production)" 

------------------------------
Best Regards
Muhammad Eissa
------------------------------

#PlanningAnalyticswithWatson

Thanks Ryan,

Really appreciate your reply.

Best regards

------------------------------
Muhammad Eissa
------------------------------

Original Message:
Sent: Wed September 23, 2020 05:24 PM
From: Ryan Clapp
Subject: Server.log flooded with messages when add log4j.logger.TM1.Lock.CriticalSection=DEBUG

The criticalSection logger is not low cost. criticalSections are a key component to how software manages memory

https://en.wikipedia.org/wiki/Critical_section

 

The "low cost" logger in that technote is the Lock.Exception logger.

Hi Muhammad,

Take a look at this article: https://www.ibm.com/support/pages/write-tm1-server-debug-logging-alternate-file

This provides an example of the DEBUG logging you want for Lock Contention.  It also shows how to write the DEBUG logging to a separate log file so the tm1server.log file does get too 'busy'.

------------------------------
Stuart King
IBM Planning Analytics Offering Manager
------------------------------

Thanks Stuart,

That's definitely useful.

------------------------------
Muhammad Eissa
------------------------------

Original Message:
Sent: Thu September 24, 2020 08:18 AM
From: STUART KING
Subject: Server.log flooded with messages when add log4j.logger.TM1.Lock.CriticalSection=DEBUG

Hi Muhammad,

Take a look at this article: https://www.ibm.com/support/pages/write-tm1-server-debug-logging-alternate-file

This provides an example of the DEBUG logging you want for Lock Contention.  It also shows how to write the DEBUG logging to a separate log file so the tm1server.log file does get too 'busy'.

------------------------------
Stuart King
IBM Planning Analytics Offering Manager
------------------------------