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.

Sign up for GitHub

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

Jump to bottom

Rare cases where messages arrive on the wrong port #37

Closed
timhutton opened this issue May 27, 2016 · 1 comment
Closed

Rare cases where messages arrive on the wrong port #37

timhutton opened this issue May 27, 2016 · 1 comment
Assignees
@timhutton
Labels
P1

Comments

@timhutton
Copy link
Contributor

Very occasionally we see the situation where observations arrive on the mission control port, for example. Other combinations too. These messages are rejected but that means losing data for that mission.
@timhutton timhutton added the P1 label May 27, 2016
@timhutton timhutton mentioned this issue Jun 2, 2016
Closed
@timhutton
Copy link
Contributor Author

Debugging showed that cause was found to be double-booked ports on the agent side: two servers both choosing the same port. Clearly this shouldn't happen.

timhutton pushed a commit that referenced this issue Jun 2, 2016
Minor: updated changelog with fix for #37.
04e867e
@timhutton timhutton mentioned this issue Jun 2, 2016
Merged
@JustinS6626 JustinS6626 mentioned this issue Mar 3, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@timhutton timhutton

Labels
P1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@timhutton