Support for detecting free port in range #16
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Port property can now be a range such as 8000-8100. This allows for a port to be in use and to select another one (one use case is when more than one agent on same server).
|
Thank you! |
|
No, I'm sorry. I am a .Net developer and don't have a Java compiler. |
I managed to work out how to compile - still not tested but at least fixed the compile errors
|
I managed to work out how to compile - still not tested (haven't worked out how to produce correct jar) but at least fixed the compile errors |
|
Ok. Thank you. I'll try to check it at weekend. |
EKibort
added a commit
that referenced
this pull request
Mar 21, 2015
Merged pull request "Support for detecting free port in range #16 " You can specify port range like 8081-8091, will be tries to random port from range. Known issues: 1. If all ports from range will be busy plugin stucks.
|
Thank you. |
ghost
mentioned this pull request
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Port property can now be a range such as 8000-8100. This allows for a
port to be in use and to select another one (one use case is when more
than one agent on same server).
Please note that I am not a Java developer and this was written in a text editor and not tested :(
Sorry!