D
dbeavon
Guest
OK thanks Irfan. That is what I suspected. But given that there is a REST API to trim inactive ABL sessions, it seems like I might be overlooking some property that constrained the ABL session lifetime, based on a sesssion lifetime limit or an idle session timeout. I didn't know if I was overlooking anything.. I suppose that trimming an inactive MS-agent has a similar effect as trimming inactive ABL sessions. (By trimming the agent process, the sessions are implicitly trimmed as well. But restarting the agent again in the future is more costly than restarting an ABL session.) Currently my idle resource timeout is zero (the default) and I'm little hesitant to mess with that since I think it affects various other resources in addition to the MS-agent. It would be nice if the various resource timeouts were managed independently of each other. I think the way you explained it in the past, the "idle resource" timeout behaves like a gated on or off switch for all of the other timeout properties. That is a bit intimidating, because we don't normally want to risk unintended consequences that might arise from introducing a timeout in an unrelated "broker resource", other than the MS-agent itself.
Continue reading...
Continue reading...