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

[CBRD-24511] Change java_stored_procedure_uds param's behavior #3872

Merged
merged 13 commits into from
Oct 18, 2022

Conversation

hgryoo
Copy link
Member

@hgryoo hgryoo commented Oct 13, 2022

@hgryoo hgryoo self-assigned this Oct 13, 2022
@hgryoo hgryoo merged commit 5a1d9f8 into CUBRID:develop 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants