Is there a blasadmin setting that can limit the maximum number of work item threads any single job can use to do its work, rather than relying on the user/job creator to rely on setting the 'Number of Targets to Process in Parallel' option?
We have a multitenant environment and sometimes the end users either inadvertently or maliciously eat up all of our app servers' Work Item threads for their patching jobs, locking all other tenants out from doing their work.
ACS, A Xerox Company
you can limit the overall number of max work item threads for the instance in blasadmin, you can also force a default job parallelism setting, but the user can still modify it when they create the job.
this is a good rfe to submit - it would be to disallow the user from overriding the default parallelism setting.