Hi Experts,
A process causes Wait:IXC lock when triggered from Apliqo UX, and it rolls back; however, when we trigger it from Arc or Architect, we do not observe the same lock in the session tab or logs.
Could you please suggest a way to find what causes the lock ?
Hi, I think you can enable TM1 lock logging in debug mode. Then, you’ll find details about the locking processes in the lock.log file (depending on your configuration).
ok, thank you very much
I activated lock logs, and we get locks because of control object as above, what might be the source of problem in }CubeProperties cube, I know cube log parameter info stored in this cube
Yes，if you use cubesetlogchangs in TI，then that TI will block other TIs possibly（as if other TIs also use that function to control TX Logging）, according to my experience, if you want to reduce lock contention between TIs，you would better use Function Cellputs YES/NO to control TX logging.
