FISH-6481: upgrading corba version to fix duplicate socket connections #5941
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
breakponchito
added
PR: DO NOT MERGE
|
Jenkins test please |
Pandrex247
approved these changes
Sep 22, 2022
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.
Upgrading corba version to fix duplicate socket connections
Description
this is a bug fix
This is an upgrade of the corba dependency with the fix to solve issue causing duplicate connections when solving hostname on the cloud environment
Important Info
Blockers
Testing
New tests
Testing Performed
This was tested on AWS cloud environment with two instances created. One for the DAS and the second one to execute client application added on the ticket as an attachment here: FISH-6481
Testing Environment
AWS cloud with two windows server 2019 instances, azul jdk 8
Documentation
Notes for Reviewers