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

Restore the ability to put the RTI on a remote machine #1164

Merged
merged 3 commits into from
May 13, 2022

Conversation

edwardalee
Copy link
Collaborator

Somewhere along the way, the ability to specify a remote machine for the RTI, e.g.:

federated reactor at wessel.eecs.berkeley.edu { ... }

got broken. The generated script was incorrect and would fail to start the RTI. Now it works, although there is a rather ad hoc five second wait for the RTI to start up.

@edwardalee edwardalee requested a review from lhstrh May 12, 2022 13:38
Copy link
Contributor

@Soroosh129 Soroosh129 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

The ad-hoc wait time is an unfortunate side-effect of the way federates actually look for the RTI (by rotating through thousands of network ports).

@edwardalee edwardalee merged commit 05084b5 into master May 13, 2022
@edwardalee edwardalee deleted the restore-remote-rti branch May 13, 2022 03:08
@petervdonovan petervdonovan added the bug Something isn't working label May 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working federated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants