Can someone explain how PA holds locks on threads in IX Mode?  Also a brief explanation on when PA executes the ExecuteRESTRequest Function.

9092   [395]   DEBUG   2022-10-18 10:37:36.146   TM1.Lock.Exception   Throwing IXConflict on object Account
9092   [395]   DEBUG   2022-10-18 10:37:36.146   TM1.Lock.Exception   CommitActionLog::Rollback: Called for thread '9092' of user 'CAMID("AD_LDAP:u:e1541ef23484b34b8fc8bb7237241b61")' executing request 'GET /api/v1/ActiveUser'.
4688   []   WARN   2022-10-18 10:37:53.961   Event.Thread   Thread[5888] has been running for 600(s).
3392   [398]   DEBUG   2022-10-18 10:39:16.507   TM1.Lock.Exception   Contention encountered attempting to acquire lock (0x000002221F7656D8) on object [Dimension "Account", addr=0x000002221F765610, index=R-5785] in READONLY mode at C:\var\jenkins\workspace\Build-tm1_main-tm1server-Win64-Production\src\tm1server\prod\tm1_r7s\TM1ObjectImpl.cpp:331 during request 'GET /api/v1/ActiveUser'. Entering wait state 'IXC'.
Blocked by the following 1 thread:
Thread 5376 holds the lock in IX mode


Thanks.

Chuck Adams

Boston College

------------------------------
Charles Adams
------------------------------

#PlanningAnalyticswithWatson

Hey Chuck, your best bet is to look at these 2 docs

https://www.ibm.com/support/pages/how-troubleshoot-tm1-server-lock-contention

https://www.slideshare.net/paulyoungcga/tm1-planning-analytics-locking-contention-guide

The function ExecuteRESTRequest is not really the offending function but rather what request it is making. The thread was getting the active user, and to service that request it needed to aquire a lock that was not compatible with the current IntenteXclusive lock that was already being held by another thread.

------------------------------
Ryan Clapp
------------------------------