-
Notifications
You must be signed in to change notification settings - Fork 126
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
[CBRD-24511] Change java_stored_procedure_uds param's behavior #3872
Merged
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
…same like broker's
…for JAVASP_SERVER_INFO struct
…the result of status when javasp server is UDS mode
hgryoo
requested review from
beyondykk9,
ctshim,
hyunikn,
shparkcubrid and
youngjinj
October 17, 2022 05:52
ctshim
approved these changes
Oct 17, 2022
beyondykk9
approved these changes
Oct 17, 2022
shparkcubrid
approved these changes
Oct 17, 2022
hyunikn
approved these changes
Oct 17, 2022
youngjinj
approved these changes
Oct 18, 2022
hgryoo
added a commit
to hgryoo/cubrid
that referenced
this pull request
Oct 18, 2022
…D#3872) http://jira.cubrid.org/browse/CBRD-24511 java_stored_procedure_uds is introduced from 11.2. It is designed only for the DB server to determine DB server should connect with UDS or TCP with Java SP server. Regardless of the parameter, Java SP server opens a listener for both UDS and TCP. If opening the socket file for UDS fails, even if a user sets the java_stored_procedure_uds=false, the user could face an unexpected error related to the UDS socket file. So according to the java_stored_procedure_uds, only one listener will be created. DB server recognizes Java SP server's mode (UDS or TCP) by reading /var/javasp/javasp_<db_name>.info file. Implementation details: - According to the value of java_stored_procedure_uds in cubrid.conf, Java SP server reads the value, and Only the listener corresponding to the configured value is executed. - DB server's communication behavior is not changed.
mhoh3963
pushed a commit
that referenced
this pull request
Oct 18, 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-24511