cqms_nonexistent_page.html not found error in logs

[chetanvajre2014]

We've a servlet that does the search. The search executes fairly quickly but gets delayed because of these errors in the logs. This is a document search and why are these errors (though logged as info) in between query execution inside the servlet?

9.03.2016 11:16:09.227 *INFO* [54.235.186.137 [1458400569223] GET /bin/wcm/imf/support/search HTTP/1.1] org.imf.imfconnect.tgs.servlets.IMFSearchServlet Search text after trimChina
19.03.2016 11:16:13.769 *INFO* [54.235.186.137 [1458400573746] GET /content/cqms_nonexistent_page.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /content/cqms_nonexistent_page.html not found
19.03.2016 11:16:14.686 *INFO* [54.235.186.137 [1458400574671] GET /content/cqms_nonexistent_page.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /content/cqms_nonexistent_page.html not found
19.03.2016 11:16:14.815 *INFO* [jackrabbit-pool-4] org.apache.jackrabbit.core.query.lucene.IndexMerger merged 44 documents in 1089 ms into _qwkg.
19.03.2016 11:16:22.152 *INFO* [54.235.186.137 [1458400569223] GET /bin/wcm/imf/support/search HTTP/1.1] org.imf.imfconnect.tgs.servlets.IMFSearchServlet QUERY RUN IS:/jcr:root/content/dam/imf/board-meetings//element(*, dam:Asset)[(jcr:contains(jcr:content/metadata/@documentTitle, 'China*') or jcr:contains(jcr:content/metadata/@documentDescription, 'China*') or jcr:contains(jcr:content/metadata/@docKey, 'China*')) and jcr:content/metadata/@dc:format = 'application/pdf'] order by jcr:content/metadata/@documentDate descending, @jcr:score descending

[Opkar_Gill]

Hi,

"cqms_nonexistent_page.html"Is likely being called by a health check script or by your LB. Do you have such a script/setup in your system?

Regards,

Opkar

[chetanvajre2014]

It's quite possible. Our system is managed by AMS. Where should I ask our support staff to look for it?

[Opkar_Gill]

Hi,

You should ask the AMS team to look into it.

Regards,

Opkar

[leeasling · Accepted solution]

This is an AMS test to make sure the servers are running correctly, it's part of their health check.  Typically when we do a release with AMS, we have them change the health check to an actual page, rather than a non-existent page for the exact reason you've posted about.
They do sometimes push back on this, and if they do, you can simply change the log level to WARN rather than INFO and your problem will be resolved.