I have nodeProcessCountPerApplication=0 to use all the worker processes of node (as per no. of cpus) and nodeProcessCommandLine="node --inspect=0.0.0.0:9229" or nodeProcessCommandLine="node --inspect", when I check only 1 instance runs in inspect mode but no other instances were created.
I have checked the IISNode C++ code files, it shows that for debugging only 1 processCount gets created, whereas for my usecase i need to have all instances or out of all few node instances in inspect mode that is in debug mode.
Where as without --inspect switch, IISNode created more no. instances for nodeProcessCountPerApplication >0 and not equal to 1.
please let me know, how can this be achieved, so that IISNode load balances the debugging request accordingly, at the moment only 1 instance runs in inspect mode with this only 1 user can use the instance for debugging remote code in node process.
I have nodeProcessCountPerApplication=0 to use all the worker processes of node (as per no. of cpus) and nodeProcessCommandLine="node --inspect=0.0.0.0:9229" or nodeProcessCommandLine="node --inspect", when I check only 1 instance runs in inspect mode but no other instances were created.
I have checked the IISNode C++ code files, it shows that for debugging only 1 processCount gets created, whereas for my usecase i need to have all instances or out of all few node instances in inspect mode that is in debug mode.
Where as without --inspect switch, IISNode created more no. instances for nodeProcessCountPerApplication >0 and not equal to 1.
please let me know, how can this be achieved, so that IISNode load balances the debugging request accordingly, at the moment only 1 instance runs in inspect mode with this only 1 user can use the instance for debugging remote code in node process.