Pulse Locking TM1 instance
After installing the Pulse Monitor software on a single TM1 instance, the first time the overnight processes ran, we experienced an issue where a users login to Pulse seems to have locked and delayed an overnight load process.
5016 [] DEBUG 2023-09-21 19:28:46.767 TM1.Lock.Exception Deadlock detected. Thread '14520' is blocked by thread '5016'. 5016 [] DEBUG 2023-09-21 19:28:46.767 TM1.Lock.Exception Deadlock detected. Thread '5016' is blocked by thread '14520'. Thread '5016' will rollback.' 5016 [] DEBUG 2023-09-21 19:28:46.767 TM1.Lock.Exception Deadlock detected locking object 0x000000A1C0F1DCD8(0x000000A1C0F1DC10) by thread 5016 waiting for current readers to drain. 5016 [] DEBUG 2023-09-21 19:28:46.768 TM1.Lock.Exception CommitActionLog::Rollback: Called for thread '5016' of user '' executing function 'Unknown'. 5016 [] DEBUG 2023-09-21 19:28:46.879 TM1.Lock.Exception Contention encountered attempting to acquire lock (0x000000A1C1C02988) on object [Cube "}CubeProperties", addr=0x000000A1C1C02010, index=R-7331] in WRITE mode at C:\var\jenkins\workspace\Build-tm1_main-tm1server-Win64-Production\src\tm1server\prod\tm1_r7s\CommitActionLog.cpp:3429 during function 'Unknown'. Entering wait state 'WR'. Blocked by the following 1 thread: Thread 14520 holds the lock in READ mode
8008 [] DEBUG 2023-09-21 19:28:55.708 TM1.Lock.Exception Contention encountered attempting to acquire lock (0x000000A1C1801988) on object [unknown "Unknown", addr=0x000000A1C1801010, index=???-???] in READ mode at C:\var\jenkins\workspace\Build-tm1_main-tm1server-Win64-Production\src\tm1server\prod\tm1_r7s\CubeDataVersion.cpp:299 during function 'Unknown'. Entering wait state 'IXR'. Blocked by the following 1 thread: Thread 5016 holds the lock in WRITE mode
5016 [] DEBUG 2023-09-21 19:29:01.807 TM1.Lock.Exception Further explaining contention encountered by thread 8008 when attempting to acquire lock (0x000000A1C1801988) on object [Cube "usr_Elec_Trade", addr=0x000000A1C1801010, index=R-7286]