Hi Tom, So you wrote: "Your first STP starts, runs until finished, and then stops. Therefore, it's not a problem, and needs no changes." Initially I think so, but looks like the STP server response time increase because of this one STP lock one(from a few) of the process that manage all STP requests. I'm not familiar with STP server configuration, I can only suppose how it works from my not very long experience. So, lets suppose you have UI application that has one button:) , and when user click on this button 10 Ajax requests asynchronously sends to STP server, STP server should process all of them and return to UI some Json or XML, but it's not so important now. So Lets say 5 "sas" process serve these 10 STP sessions that should be processed in same time.Using firebug and task manager on server machine easy observe how these processes serves : All 5 "sas" processes serve first 5 STP sessions, then after some of session finished - it serve some another session that before waits in queue probably. So, lets go back to my problem - When I didn't run my application(with two long time execute STPs) but run this application with one button - all these 10 Ajax request will finish sequentially successfully similarly as I describe higher. Now, When I run my problematic application that creates 2 STP session that runs a few hours, - 2 from 5 processes become locked by them. Now, when I run second application with one button - logically only 3 processes should serve these 10 STP requests, but in fact what I saw - 3 sas processes serve needed requests normally(finish one, then takes next etc.), but two of requests(that were allocated to 2 locked sas process mantioned higher) can be finished and run for a long time. And these two session will ends only after another , older STPs that runs for a long time will be finished. So due all these I think next, what I do : UI -still run two Ajax to STP, but STP sessions will not executes these macros for a long time - they will just run some x(or call execute) command that will create non STP session that will execute these two macros without impacting another STP users. You wrote: My first question is to ask whether you're sure that it is a resource drain? As far as I know, on any modern capable server a process sitting there mostly in a sleep state won't impede other processes. You are absolutely right, my second STP that observe logs from first STP uses sleep function that doesn't eat almost any cpu time, but anyway STP process is active, it doesn't unlocks on time,when sleep function executes, it lock sas process and keep it on serving only this one concrete session, as I understand. Have you done any testing to measure this effect? If it's very minor (which is what I would predict), just keep your code the way it is. Yes, I made the tests, I described results higher(UI with one button, 10 STPs and another UI with this 2 long-run STPs). Tom, as I wrote higher I am not the specialist on Admin part of STP server configuration, I'm not 100% sure how STP session are distributed between "sas" process that serve them, but even from general logic it looks a little bit not elegant to lock two(lets say from 5) sas processes that manage hundreds of users STP requests(majority of them executes quick, second-two)... I don't think that STP server purpose is manage long time processes, it rather some LSF batch stuff should do... I'm not sure , but I know that "platform process manager" tool gives possibility to run some flow on fly, by some process manage command(jrun for example). So I'll try from STP session create some x command that will send correct command to platform process manager that will run(on demand...) some flow with two jobs that will have UW code with needed macros(one run long executed macro, second - observe it logs)... Paradox of this task is the fact that it's very similar to usual task, with only one difference - macro executes long time and therefore all problems occurs, but anyway it's the interesting things and I hope I'll finish it this year:). Thanks!
... View more