Next available port is not chosen
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- java
- Domain
- backend, networking
Research direction
Start by locating the port-binding entry point in the Java code and checking how an unavailable port is currently handled. Implement the behavior described in the issue: try successive ports when the requested port is occupied, and verify that binding succeeds on the next available port.
Written by the indexing model from the issue text.
Description
Hey Thomas,
The old shadow-undertow library would attempt to bind to the next available port when the port to bind to was unavailable (e.g. if something is already bound to 3000, it would bind to 3001; if 3001 is unavailable, it would bind to 3002, etc).
- Dominant language
- Java
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from thheller/shadow-http
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
thheller/shadow-http#1 ·
All issues in thheller/shadow-http
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
[BUG]茶杯方块在取茶时会引发崩溃 Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
1.0.0-alpha2 Type/Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wso2/dpdp-accelerator#272 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
area/frontend
Difficulty 2/5 1-3 hours Newbie friendliness 65/100