Maybe this is something I should have done a lot earlier, but with the app now bedded in and working, I've got spare time to play around with other things.
So I triggered "Active Processes" from the standard menu and discovered 566 processes - all in the "Waiting" state at 0%.
Most relate to the members interface where I guess maybe there is more of a danger members will close the browser rather than Logout - I'll need to look at this - but 4 questions
1) Is there a secret "Cancel all Processes" command (doing 566 one at a time is going to be a real pain.
2) What is the likely cause (how long is a piece of string)
3) Is there anything I can put in the Logout Notification to kill a session's active processes (or preferably just certain ones)
4) will 566 active processes be causing me any performance issues (haven't noticed any)
