Massive No lock messages when saving data happens concurrently

Post Reply
User avatar
macsir
Community Contributor
Posts: 695
Joined: Wed May 30, 2012 6:50 am
OLAP Product: TM1
Version: PAL 2.0.8
Excel Version: Office 365
Contact:

Massive No lock messages when saving data happens concurrently

Post by macsir » Wed Mar 18, 2020 1:58 am

I know it is warning but there are massive "No lock" info in the sever log when two saving processes running at the same time. Is there a way to suppress this? And how to get this C++ source code by the way? :)
13428 [1f43] WARN 2020-03-18 11:09:33.160 TM1.Lock Attempt to release lock on 0x00000191F23D1A68(0x00000191F23B9A10). No lock held by module c:\jenkins\j12\workspace\build-tm1_main-tm1server-win64-production\src\tm1server\prod\tm1_r7s\tm1serverimpl.cpp at Line 16703
13428 [1f43] WARN 2020-03-18 11:09:33.162 TM1.Lock Attempt to release lock on 0x00000191F23D1A68(0x00000191F23B9A10). No lock held by module c:\jenkins\j12\workspace\build-tm1_main-tm1server-win64-production\src\tm1server\prod\tm1_r7s\tm1serverimpl.cpp at Line 16703
1
In TM1,the answer is always yes though sometimes with a but....
http://tm1sir.blogspot.com.au/

User avatar
ykud
Posts: 102
Joined: Sat Jan 10, 2009 10:52 am
Contact:

Re: Massive No lock messages when saving data happens concurrently

Post by ykud » Wed Mar 18, 2020 2:16 am

You can configure tm1s-log.properties file to record only ERROR and above for Lock component by adding a line like this:
log4j.logger.TM1.Lock=Error

Post Reply