TM1Top session stuck with 'Run' under the 'State'

yagami_ren

We've had a couple instances where users sessions get stuck with 'Run' under the 'State' header...but nothing is actually running. This occurs when a user crashes out of excel while talking to TM1 and they are able to log back in. The troubling thing is that we cannot get rid of the old session which is stuck with 'Run' showing as the state.

There is nothing under 'Function', Obj Lock Status', 'User Lock Status', or 'Time(s)'...and it's not blocking anyone. But we should be able to kill the thread, end the session, disconnect the user, or something...but all attempts to eliminate it from TM1Top have failed. It only goes away after a restart.

The problem is that we have overnight chores that look at TM1Top to make sure nothing is running before it start running its processes. This is how we determine a multi-threaded chore has completed before starting the next chore.

With 'Run' showing up in the 'State' the chores think its still working on previous chore and never kicks off the next one.

6235999

terry720 wrote:The problem is that we have overnight chores that look at TM1Top to make sure nothing is running before it start running its processes.

I would never tie anything to TM1TOP. It can be a nice little tool to see what's going on but it's definitely not ready for prime time when it comes to using it as part of an automated process. YMMV.

dada19891101

We built a home grown chore manager that allows chores to be multi-threaded. the trick is that all the threads need to complete before the next chore is kicked off or you risk locking/blocking by the upstream processes.  The first thing we do is kick out all the users so that no one is logged in and nothing is running.

TM1Top does a good job of displaying the status of the mutli-threaded processes and our Chore Manager is able to check TM1Top every minute until all the threads complete.  Once nothing is running...it kicks off the next process. This runs pretty much flawlessly but we recently ran into a situation where a user was stuck in a 'Run' state but had been logged out for hours.

It wasn't an issue with TM1Top afterall...the user was actually in a Run state according to the transaction logs...but it was simply filling up the log with SSL errors. We weren't able to kill it or remove the user...ended up having to restart the instance to get it to stop.

Not good...

a23742212

Hi ,

Its resolved in TM1 9.5.2 FP3

Check https://www-304.ibm.com/support/entdocv ... wg1PM57320

Its the same issue. User operation in progress and user closes / crashes the client and 100s of erros logged in..

Thanks ...