Aug 13 2021 02:15 PM
The powershell code in the MSIX Toolkit "Batch Conversion" seems to imply that a controller may work with many different worker VMs in parallel. Each parallel thread would invoke a separate instance of the local MMPT to work with a counter-part on a different remote VM.
I wanted to ask if the MMPT is truly multi-threaded to support this. While my testing shows OK results for a couple of worker VMs, expanding beyond that seems to cause unexpected (and inconsistent) failures. Of course there is always the possibility of resource exhaustion occurring at some point in the chain, but I wanted to be sure that this is a supported scenario.
I want to package up a very large group of apps and want to utilize 8 worker VMs (spread out on different Hyper-V hosts). My modified scripts work OK on two workers, but going above 3 seems an issue.
Aug 19 2021 04:14 PM
Aug 24 2021 08:42 AM
Thanks for the confirmation.
I am attaching an of the example failure log files. If I rerun the exact same scenario, some of these will work and others fail instead. The failures tend to appear in two places:
Even when this condition exists, I am able to log into the problematic VM remotely or run remote PowerShell commands to it manually, so even if this is an environmental issue, the packaging tool seems to be more sensitive to it.
I have since checked out the environment further and found that one of the AD controllers seems to have had an issue with Patch Tuesday updates. This is being repaired and I'll rerun the tests to see if it solved the issue.
Aug 24 2021 08:44 AM
@ShakersMSFT Here is that example log file.
Aug 25 2021 08:43 AM
@ShakersMSFT I have some progress to report.
I am now running with three worker VMs without issue and will soon try to expand to more.