Depends what is actually running for the requestor. If interaction is still running activities or doing things where it runs through certain parts of the engine (I dont have list), you can "interrupt" the requestor [set a trap condition where the engine will recognize that you've asked to stop the interaction]. If you're stuck in java bits that are not making appropriate engine calls you're out of luck -- Java doesnt really have a proper method to kill thread.

What is the thread doing that leads you to OOM condition?

Hi Werda,

This is for long running requestors, for example if a manager tries to extract a report that is too big in volume , the requestor is in process of gather all required data and building the stream for export.This for instance if it takes more than 10 mins and we wish to terminate the requestor while it is in middle of processing the request as we suspect it can bring the server down, how can we do it. In SMA when the requestor is locked we cannot kill it , we have to wait for requestor to complete processing before we can stop it.It usually results in OOM exception and the server auto recovers , but not before other users are affected.I understand specific scenarios can be prevented by process changes, but in general how can one handle such scenarios.