TM1 Forum

Every once and awhile a user will generate a view or subset that generates and inordinate amount of locking.

Is there a parameter or process that sets a maximum user generated lock?

Typically if the lock is over 100 seconds the lock is indefinite. It would be great to set that as a maximum and if exceeded would disconnect the user or cancel the thread.

I have heard ReceiveProgressResponseTimeoutSecsmight might work, has anyone had success with that parameter?

Thanks!

As far as an automated method of killing a user, we have created a windows service using the C/C++ API that will consume TM1TOP and kill locking processes after a threshold is met. We did it as a windows service because the the processes starts a TM1TOP instance and there are times that locks will prevent TM1TOP from opening, this way it is always logged in.

Looking at your signature you say you are using 9.1 and 10.1. Which system is having the locks occur? If this is the 10.1 instance then you may want to track down the cause of the locks. With parallel interaction and the other improvements locking should not be a frequent thing.

George I wanted to thank you for replying.

Our new system is in 10.1 and each lock is unique so it it is hard to plan around.

So from my understanding the only way to stop a transaction is to do it through custom code.

There used to be an issue with the client and servers losing track of each other which. This usually showed up as the hung user with an "ObjectDuplicate()" status in TM1Top.

http://www.tm1forum.com/viewtopic.php?p=9378

Are you talking about broken threads that never recover or threads that you'd like to kill becuase a user asked for too much?

If its broken threads then the cfg might help. Let us know as I think the specific Object Duplicate bug doesn't exists anymore so if the same kind of thing is happening again it would be good to know.

Cheers