Wrong Query happened for particular asset 11 times | Community
Skip to main content
S
SreeDurga
April 2, 2021
Solved

Wrong Query happened for particular asset 11 times

  • April 2, 2021
  • 2 replies
  • 817 views

Wrong Query happened for particular asset 11 times
(1st occurence 12:39:45 & Last occurence 12:39:45)
24.02.2021 12:39:45.693 *WARN* [10.43.32.87 [1614170383638] GET /libs/wcm/core/content/reference.json HTTP/1.1]
org.apache.sling.event.impl.jobs.JobManagerImpl
Query syntax wrong /jcr:root/var/eventing/jobs//element(*,slingevent:Job)
[@event.job.topic = 'com/day/cq/replication/job/offloading_outbox' and not(@slingevent:finishedState)
and ((@cq:path = '/content/dam/diagnostics/Blueprint/en/videos/rmd/Fighting-To-Beat-Lung-Cancer-Bobbi's-Story-of-Hope.mp4'))]
order by @slingevent:created ascending
org.apache.sling.api.resource.QuerySyntaxException: java.text.ParseException: Query:
/jcr:root/var/eventing/jobs//element(*,slingevent:Job)[@event.job.topic =
'com/day/cq/replication/job/offloading_outbox' and not(@slingevent:finishedState)
and ((@cq:path = '/content/dam/diagnostics/Blueprint/en/videos/rmd/Fighting-To-Beat-Lung-Cancer-Bobbi's-Story-of-Hope.mp4(*)'))]
order by @slingevent:created ascending

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Shubham_borole

@sreedurga 
It looks like the error/warning is associated to a particular asset only. It will help to see the query that was used. However can you try to see

1. if there is a scope to do escaping in query or

2. try to make same query using AEM query builder (assuming current query is happening via code)

2 replies

Kiran_Vedantam
Community Advisor
Kiran_VedantamCommunity Advisor
Community Advisor
April 2, 2021

Hi @sreedurga,

 

Can you please elaborate on your query?

 

Thanks,

Kiran Vedantam.

    Shubham_borole
    Community Advisor
    Shubham_boroleCommunity AdvisorAccepted solution
    Community Advisor
    April 5, 2021

    @sreedurga 
    It looks like the error/warning is associated to a particular asset only. It will help to see the query that was used. However can you try to see

    1. if there is a scope to do escaping in query or

    2. try to make same query using AEM query builder (assuming current query is happening via code)

      Terms & ConditionsAccessibility statement

      Loading footer...