I have three active processes that are still running (from 10th June 2023. I cannot kill them off from within the user admin interface. they just won't "Cancel" So maybe using MySQL workbench or similar, is there a way I can kill these without having to bring down the server. They are preventing me from publishing a new version
*EDIT* I have deleted the offending active processes from Execution context but AIM still comes back and says there are active processes still running
Supplementary question - why does this keep happening? A couple of months ago I found 250+ processes in "Execution context"
Active Processes stuck
Active Processes stuck
Rocketman
V8.7 Developer Edition. Server 2016 Standard edition. MySql 5.5
V8.7 Developer Edition. Server 2016 Standard edition. MySql 5.5
Re: Active Processes stuck
UPDATE I restarted the server - but surely I shouldn’t have to do this? also Execution Context records needs a couple of more attributes in my opinion
1) Process started tinestamp
2) Business space that triggered it
PLUS a kill switch that works no matter what
1) Process started tinestamp
2) Business space that triggered it
PLUS a kill switch that works no matter what
Rocketman
V8.7 Developer Edition. Server 2016 Standard edition. MySql 5.5
V8.7 Developer Edition. Server 2016 Standard edition. MySql 5.5
Re: Active Processes stuck
1+rocketman wrote: ↑Sat Jul 01, 2023 9:28 am UPDATE I restarted the server - but surely I shouldn’t have to do this? also Execution Context records needs a couple of more attributes in my opinion
1) Process started tinestamp
2) Business space that triggered it
PLUS a kill switch that works no matter what
Henrik (V8 Developer Ed. - Windows)