[
https://issues.apache.org/jira/browse/OLINGO-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milko Todorov updated OLINGO-1262:
----------------------------------
Description:
Hello Olingo community,
we have an issue when sending multiple queries packed in batch request. Often
upon restart of our application (when the caches are empty), the first
execution of a particular batch request which contains quite a number of
queries we are getting one of the following errors (most of the time the first
one):
{color:#d04437}!/jira/images/icons/emoticons/error.png! You have attempted to
set a value of type class java.lang.String for parameter 5 with expected type
of int from query string {color}
{color:#d04437}SELECT E1 FROM CreditProduct E1 WHERE
(((E1.creditProductPk.creditAgencyId = ?2) AND ((E1.creditProductTypeCode = ?5)
OR (E1.creditProductTypeCode = ?8))) AND (E1.isDeactivated = false)).{color}
{color:#d04437}!/jira/images/icons/emoticons/error.png! Query argument 33 not
found in the list of parameters provided during query execution.{color}
{color:#d04437}!/jira/images/icons/emoticons/error.png! While trying to invoke
the method java.lang.String.contains(java.lang.CharSequence) of a null object
returned from
org.apache.olingo.odata2.jpa.processor.core.ODataParameterizedWhereExpressionUtil.getJPQLStatement(){color}
{color:#d04437}!/jira/images/icons/emoticons/error.png! Query argument 3 not
found in the list of parameters provided during query execution.{color}
{color:#333333}It looks like that the issue could be in class
{color}*ODataParameterizedWhereExpressionUtil* where the
*parameterizedQueryMap* is defined. It is defined as static and it looks like a
concurrency issue. Is there a reason behind defining this map as static? It
seems very similar to the already opened issue
[OLINGO-1254|https://issues.apache.org/jira/browse/OLINGO-1254]
As soon as the queries runs one time and the caches are filled we don't have it
anymore unless the app is restarted.
Could you please assist us with finding a solution here?
Thank you,
Milko
was:
Hello Olingo community,
we have an issue when sending multiple queries packed in batch request. Often
upon restart of our application (when the caches are empty), the first
execution of a particular batch request which contains quite a number of
queries we are getting one of the following errors (most of the time the first
one):
{color:#d04437}!/jira/images/icons/emoticons/error.png|width=16,height=16,align=absmiddle!
You have attempted to set a value of type class java.lang.String for
parameter 5 with expected type of int from query string {color}
{color:#d04437}SELECT E1 FROM CreditProduct E1 WHERE
(((E1.creditProductPk.creditAgencyId = ?2) AND ((E1.creditProductTypeCode = ?5)
OR (E1.creditProductTypeCode = ?8))) AND (E1.isDeactivated = false)).{color}
{color:#d04437}!/jira/images/icons/emoticons/error.png|width=16,height=16,align=absmiddle!
Query argument 33 not found in the list of parameters provided during query
execution.{color}
{color:#d04437}!/jira/images/icons/emoticons/error.png|width=16,height=16,align=absmiddle!
While trying to invoke the method
java.lang.String.contains(java.lang.CharSequence) of a null object returned
from
org.apache.olingo.odata2.jpa.processor.core.ODataParameterizedWhereExpressionUtil.getJPQLStatement(){color}
{color:#d04437}!/jira/images/icons/emoticons/error.png|width=16,height=16,align=absmiddle!
Query argument 3 not found in the list of parameters provided during query
execution.{color}
{color:#333333}It looks like that the issue could be in class
{color}*ODataParameterizedWhereExpressionUtil* where the
*parameterizedQueryMap* is defined. It is defined as static and it looks like a
concurrency issue. Is there a reason behind defining this map as static?
As soon as the queries runs one time and the caches are filled we don't have it
anymore unless the app is restarted.
Could you please assist us with finding a solution here?
Thank you,
Milko
> Executing multiple queries in batch request leads to parameters mismatch /
> not found
> ------------------------------------------------------------------------------------
>
> Key: OLINGO-1262
> URL: https://issues.apache.org/jira/browse/OLINGO-1262
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
> Affects Versions: V2 2.0.10
> Reporter: Milko Todorov
> Priority: Major
>
> Hello Olingo community,
> we have an issue when sending multiple queries packed in batch request. Often
> upon restart of our application (when the caches are empty), the first
> execution of a particular batch request which contains quite a number of
> queries we are getting one of the following errors (most of the time the
> first one):
> {color:#d04437}!/jira/images/icons/emoticons/error.png! You have attempted
> to set a value of type class java.lang.String for parameter 5 with expected
> type of int from query string {color}
> {color:#d04437}SELECT E1 FROM CreditProduct E1 WHERE
> (((E1.creditProductPk.creditAgencyId = ?2) AND ((E1.creditProductTypeCode =
> ?5) OR (E1.creditProductTypeCode = ?8))) AND (E1.isDeactivated =
> false)).{color}
> {color:#d04437}!/jira/images/icons/emoticons/error.png! Query argument 33
> not found in the list of parameters provided during query execution.{color}
> {color:#d04437}!/jira/images/icons/emoticons/error.png! While trying to
> invoke the method java.lang.String.contains(java.lang.CharSequence) of a null
> object returned from
> org.apache.olingo.odata2.jpa.processor.core.ODataParameterizedWhereExpressionUtil.getJPQLStatement(){color}
> {color:#d04437}!/jira/images/icons/emoticons/error.png! Query argument 3 not
> found in the list of parameters provided during query execution.{color}
> {color:#333333}It looks like that the issue could be in class
> {color}*ODataParameterizedWhereExpressionUtil* where the
> *parameterizedQueryMap* is defined. It is defined as static and it looks like
> a concurrency issue. Is there a reason behind defining this map as static? It
> seems very similar to the already opened issue
> [OLINGO-1254|https://issues.apache.org/jira/browse/OLINGO-1254]
> As soon as the queries runs one time and the caches are filled we don't have
> it anymore unless the app is restarted.
> Could you please assist us with finding a solution here?
> Thank you,
> Milko
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
