Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple node worker instances for Remote debugging: Can't run the all node instances with "--inspect" flag when provided in web.config parameter #690

Open
Anurag9589 opened this issue Sep 28, 2021 · 0 comments

Comments

@Anurag9589
Copy link

Anurag9589 commented Sep 28, 2021

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.

@Anurag9589 Anurag9589 changed the title Can't run the all node instances with "--inspect" flag work with web.config parameter Can't run the all node instances with "--inspect" flag when provided in web.config parameter Feb 1, 2022
@Anurag9589 Anurag9589 changed the title Can't run the all node instances with "--inspect" flag when provided in web.config parameter Multiple node worker instances for Remote debugging: Can't run the all node instances with "--inspect" flag when provided in web.config parameter Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant