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

Change SocketBasedRemoteExecutor to use LocalPlatform AvailablePortIterator #254

Open
brianoliver opened this issue Jun 20, 2015 · 2 comments

Comments

@brianoliver
Copy link
Contributor

While we correctly use ephemeral ports to create ServerSockets for the SocketBasedRemoteExecutor, there's a possibility that ports provided by the AvailablePortIterator may accidentally be taken by the SocketBasedRemoteExecutor prior to an application starting, especially when the AvailablePortIterator port range overlaps with the operating system ephemeral port range.

The simple solution is to use the AvailablePortIterator (and keep trying) when creating a SocketBasedRemoteExecutor.

@brianoliver
Copy link
Contributor Author

Reported by @brianoliver

@brianoliver
Copy link
Contributor Author

This issue was imported from JIRA ORACLETOOLS-254

@brianoliver brianoliver self-assigned this May 16, 2016
@brianoliver brianoliver modified the milestone: 2.0.0-SNAPSHOT May 16, 2016
@brianoliver brianoliver added this to the 4.x milestone Jul 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant