Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

graphql does not denote a Persistent Query Path

Avatar

Level 4

Hi Team, getting this response when I execute a AEM servlet which internally calls graphql endpoint and will pass the response to AEM servlet.

 

{
"data": "{\"errors\":[{\"errorType\":\"ServletError\",\"message\":\"Internal Servlet Failure\",\"details\":\"Path: 'test/..../.../.....' does not denote a Persistent Query Path\"}]}",
"status": 500
}

 

any idea on this? 

 

Thanks!!

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 4

Solution:

The issue "does not denote a Persistent Query Path" occurs when you are executing the graphql endpoint and graphql endpoint contains special characters then we will get this internal servlet failure,  does not denote a Persistent Query Path.

 

To fix this, make sure that graphql endpoint doesn't contain special character. In my case ; was causing the issue.

Issue URL: http://localhost:4502/graphql/execute.json/myproject/namesByPath;path=/content/dam/test/......

Working URL:  http://localhost:4502/graphql/execute.json/myproject/namesByPath%3Bpath=/content/dam/test/......

Difference is issue url contains ; and working url contains encoded value of semicolon i.e. %3B. 

 

FYR: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/graphql...

 

@Shashi_Mulugu @MayurSatav @kautuk_sahni 

View solution in original post

3 Replies

Avatar

Community Advisor

@Uppari_Ramesh did u try to execute graphic query directly? Is it working? Can you also post your servlet code, so that we can guide you better???

Avatar

Level 4

Hi @Shashi_Mulugu ,

 

When I execute the graphql endpoint directly, it's working fine. The servlet code that I'm using is working in all environments except one author instance. This is a intermittent issue. Unable to find what could be the issue. 

Avatar

Correct answer by
Level 4

Solution:

The issue "does not denote a Persistent Query Path" occurs when you are executing the graphql endpoint and graphql endpoint contains special characters then we will get this internal servlet failure,  does not denote a Persistent Query Path.

 

To fix this, make sure that graphql endpoint doesn't contain special character. In my case ; was causing the issue.

Issue URL: http://localhost:4502/graphql/execute.json/myproject/namesByPath;path=/content/dam/test/......

Working URL:  http://localhost:4502/graphql/execute.json/myproject/namesByPath%3Bpath=/content/dam/test/......

Difference is issue url contains ; and working url contains encoded value of semicolon i.e. %3B. 

 

FYR: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/graphql...

 

@Shashi_Mulugu @MayurSatav @kautuk_sahni