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

[2.7] WebLogic Server test fixes - Ordinal binding vs Named binding #2111

Merged
merged 1 commit into from
Apr 17, 2024

Conversation

rfelcman
Copy link
Contributor

This is fix for intermittent WebLogic Server test error.

Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.7.15.v20240103-592473ae33): 
org.eclipse.persistence.exceptions.DatabaseException Internal Exception: java.sql.SQLException: ORA-17090: Operation not 
allowed: Ordinal binding and Named binding cannot be combined! https://docs.oracle.com/error-help/db/ora-17090/
Error Code: 17090 Call: BEGIN SProc_Read_Address(?, ?, ?, ?, ?, ?); END; bind => [6 parameters bound] Query: 
readAllQuery(name="SProcAddressByIndex" referenceClass=Address )

There is named query SProcAddressByIndex in org.eclipse.persistence.testing.models.jpa.advanced.Address called by org.eclipse.persistence.testing.tests.jpa.advanced.AdvancedJPAJunitTest#testNamedStoredProcedureQueryByIndex()
where parameters are passed by index
and there is similar query SProcAddress and test org.eclipse.persistence.testing.tests.jpa.advanced.AdvancedJPAJunitTest#testNamedStoredProcedureQuery() where parameters are passed by name. WebLogic datasource statement cache doesn't distinguish these queries and in some case testNamedStoredProcedureQueryByIndex fails.

Signed-off-by: Radek Felcman <radek.felcman@oracle.com>
@rfelcman rfelcman merged commit 825c73d into eclipse-ee4j:2.7 Apr 17, 2024
6 checks passed
@rfelcman rfelcman deleted the mats_test_fix_2.7 branch April 17, 2024 07:16
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.

2 participants