Recover if the randomly-assigned port is already in use #1688

New Issue

fergalmoran · 2025-08-09T17:21:30Z

fergalmoran commented

2025-08-09 17:21:30 +00:00

Originally created by @SteveSandersonMS on 11/17/2015

The out-of-process Node host opens a server on port zero, which means "let Node or the OS decide". AFAIK this is implemented inside Node as "pick a random port without checking whether it's in use or not". Ideally, if the randomly-chosen port is in use, we should keep retrying until we get an available port.

*Originally created by @SteveSandersonMS on 11/17/2015* The out-of-process Node host opens a server on port zero, which means "let Node or the OS decide". AFAIK this is implemented inside Node as "pick a random port without checking whether it's in use or not". Ideally, if the randomly-chosen port is in use, we should keep retrying until we get an available port.

fergalmoran closed this issue

2025-08-09 17:21:30 +00:00

fergalmoran added the enhancement core P1 enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement core core P1 labels 2025-08-09 17:21:31 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#1688