Does TI Process Spawn Threads?

[raeldor]

Hi,

We have another odd issue. When a user loads a template, they wait for all the views to refresh. Then they push a button in PAW that launches a TI process. We then see something strange. We see 3 active threads for that user. 2 of them are blocking each other. One thread is the execution of the TI process; that is blocked on a cellset retrieve from the same user. There is also a separate executeMDX thread for the same user.

Do TI processes spawn threads to work in parallel? Could that be causing locking with itself? Is it possible the 'refresh on completion' for the button is launching the refresh of the views before the TI process is complete? We're very confused how a single user can have multiple threads running. The user has confirmed no other tabs open.

Thanks
Ray

[Steve Rowe]

PAW will use a thread per widget (mostly, I think!) on the page, depending on how you have the action button configured and the content on the screen the button could be recalculating any data on the screen. If this is long running I guess it could be running at the same time as the action button TI call.

Alternatively if the TI has a datasource (and depending on your server config) it could be spawning multiple threads to calculate the datasource and so the TI needs to wait until the view is calculated until it starts processing it.

If you run the TI as a chore (just to test) you should be able to see if the threads are part of the TI or part of the PAW screen.

[raeldor]

Thank you. It turned out what was going on here was that views were timing out with no error message being returned, and the user hit the button again thinking the views had completed. So TM1 was still running a cellset retrieve on the back end and the user was running the TI process again, which was causing the locks.