JSP file [/monitor/app_check.jsp] not found errors within Liferay logs
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
Many code_jsp 404 WARN messages such as the following are being observed in the Liferay logs:
WARN [https-jsse-nio2-11251-exec-3][code_jsp:163] {code="404", msg="JSP file [/monitor/app_check.jsp] not found", uri=/monitor/app_check.jsp}
WARN [https-jsse-nio2-11251-exec-2][code_jsp:163] {code="404", msg="JSP file [/monitor/app_check.jsp] not found", uri=/monitor/app_check.jsp}
WARN [https-jsse-nio2-11251-exec-11][code_jsp:163] {code="404", msg="JSP file [/monitor/app_check.jsp] not found", uri=/monitor/app_check.jsp}
WARN [https-jsse-nio2-11251-exec-13][code_jsp:163] {code="404", msg="JSP file [/monitor/app_check.jsp] not found", uri=/monitor/app_check.jsp}
Environment
- Liferay DXP behind an AWS Elastic Load Balancer
Resolution
- These log messages do not come from Liferay. You can examine the HTTP access logs to see which requests trigger them:
<redacted IP address> - - [date] "GET /monitor/app_check.jsp HTTP/1.1" 404 61043 "-" "ELB-HealthChecker/2.0" - "ELB-HealthChecker/2.0" indicates the request originates from the "Elastic Load Balancing" component of AWS.
- To stop the warnings:
- Change the health check path in your AWS load balancer target group to a URL that Liferay serves, such as the portal home page.
- Then, confirm that the 404 entries no longer appear in the HTTP access log.
Did this article resolve your issue ?