User bio
404 bio not found
Member since Feb 18, 2016
Replies:

Even launching multiple processes to stop services "concurrently" will never force them to halt at the exact same time. Services generally run on a polling basis and may be in different states when receiving the shutdown/disable signal. And you generally want them stop gracefully rather than interrupt whatever they're currently doing.

I wrote a utility that iterates over production items and disables or enables them, selectable by host type or name pattern. It will optionally defer updating the production status until all enable/disable operations are complete and it runs pretty quickly doing that. However, the business hosts shut down gracefully, and that may vary in duration. There's not really a good way around that.

If you're interested in the utility, I'll dig it up and share it.

If the message doesn't qualify for any of the conditions, it won't be delivered anywhere and will be purged at the end of the retention period you've set for the Ens.Util.Tasks.Purge task. Do you need to delete it immediately?

For starters, I think this:

request.GetValueAt("RGSgrp(1).AIGgrp(context.AIGitr).AIG:3)")'=""

Should actually be this:

request.GetValueAt("RGSgrp(1).AIGgrp("_context.AIGitr_").AIG:3)")'=""

Let's see what happens after you fix that.

Certifications & Credly badges:
Followers:
Following: