S
slacroixak
Guest
Hi Brian, I know my very first post is a bit long. It was already saying my current work around is an OS-COMMAND asbman -i -stopagent 
I have it running in production, and for one case my agent has run 2757 more hits before the asbman -agentstop completed its job 
(actually, it even fired that asbman command 2757 times... I've just changed the code with a new global share var to limit to one single call). So 2757 opportunities to cause a problem. Brian, I believe we need a may to make an agent tell its broker "Huston I have a problem, please remove me from the agent pool NOW and shut me down, as I must no longer process any more request" I know the PASOE offers many nice REST management API's. Is it possible to fire such a remove me from the pool synchronously? I mean, for some points, the guy that should trigger this action is the agent itself.
Continue reading...
I have it running in production, and for one case my agent has run 2757 more hits before the asbman -agentstop completed its job (actually, it even fired that asbman command 2757 times... I've just changed the code with a new global share var to limit to one single call). So 2757 opportunities to cause a problem. Brian, I believe we need a may to make an agent tell its broker "Huston I have a problem, please remove me from the agent pool NOW and shut me down, as I must no longer process any more request" I know the PASOE offers many nice REST management API's. Is it possible to fire such a remove me from the pool synchronously? I mean, for some points, the guy that should trigger this action is the agent itself.Continue reading...