[CBRD-24499] Setting CUBRID_TMP causes nativesocket bind error in Java a SP (#3871) #3878
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
…a SP (CUBRID#3871) http://jira.cubrid.org/browse/CBRD-24499 *Purpose* Setting CUBRID_TMP causes a native socket bind error because the UDS socket file is not created properly because the path is set wrongly. *Implementation* I've changed the UDS socket file path for javasp same as the broker's socket file inside of $CUBRID/var/CUBRID_SOCK/ if CUBRID_TMP is not set. If the CUBRID_TMP is set, the socket file will be created inside of the $CUBRID_TMP directory. The exact path of the UDS socket file is created in the cub_javasp utility, and it passes to the JVM.
beyondykk9
approved these changes
Oct 16, 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.
http://jira.cubrid.org/browse/CBRD-24499
Note
This patch was reverted because of CI hang problem. But the problem is not from the commit.
Purpose
Setting CUBRID_TMP causes a native socket bind error because the UDS socket file is not created properly because the path is set wrongly.
Implementation
I've changed the UDS socket file path for javasp same as the broker's socket file inside of $CUBRID/var/CUBRID_SOCK/ if CUBRID_TMP is not set. If the CUBRID_TMP is set, the socket file will be created inside of the $CUBRID_TMP directory. The exact path of the UDS socket file is created in the cub_javasp utility, and it passes to the JVM.