Commit
825c73d9fa783dc770b9a55ed331e268feb8706a
by GitHubWebLogic Server test fixes - Ordinal binding vs Named binding (#2111)
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>
(commit: 825c73d)