look at using stopSession for ending gsApplicationTools topaz jobs ...

[dalehenrich]

If there are a large number of gsApplicationTools gems running, a simple process kill can stress the shared cache maintenance processes ... using stopSession would put less stress on the system ... if needed continue to use kill to make sure that the topaz process has exited after the session ends

[dalehenrich]

Just a note ... since a seaside session can be sitting idle on a socket accept and all other non-active threads sitting on Delay's (the primary thread is on a 10 second delay and the sigabort thread is on a 30 second delay) we need to use System class>>terminateSession:timeout:, and set the timeout to a time longer than the shortest Delay (10 seconds at the moment) to avoid having the stone go ahead a use a SigTerm to kill the process, which defeats the purpose of using stopSession ...