Issue 45743: False positives when checking for Tomcat webapps

Status:closed
Assigned To:Guest
Type:Defect
Area:Core
Priority:3
Milestone:22.07
Opened:2022-06-22 11:43 by jeckels
Changed:2022-07-11 11:19 by jeckels
Resolved:2022-06-27 14:05 by Matthew Bellew
Resolution:Fixed
Related:45540, 45735
Support Ticket: 
Pull Requests:platform#3481
Closed:2022-07-07 14:45 by jeckels
2022-06-22 11:43 jeckels
Title»False positives when checking for Tomcat webapps
Assigned To»Matthew Bellew
Type»Defect
Area»Core
Priority»3
Milestone»22.07
Related»45735
Our current approach to warning about other Tomcat webapps is prone to false positives, including:

Deploy LabKey to the root context in Tomcat.
Start up the server in production mode.
Create a /docs project.
Bounce Tomcat (the check is done during startup and the results are cached).
Log in as a site admin.

You get a warning that says "This server appears to be running with one or more default Tomcat web applications that should be removed. These may include 'examples', 'docs', 'manager', and 'host-manager'"

As we discussed in chat, we should consider switching to an MBean-based approach for checking for other webapps. Possible reference code:

https://stackoverflow.com/questions/7805843/list-deployed-webapps-in-apache-tomcat

2022-06-24 13:06 Matthew Bellew
Pull Requests»https://github.com/LabKey/platform/pull/3481

2022-06-27 14:05 Matthew Bellew
resolve as Fixed
Statusopen»resolved
Assigned ToMatthew Bellew»jeckels

2022-07-07 14:45 jeckels
close
Statusresolved»closed
Assigned Tojeckels»Guest
Tested in the FB.

2022-07-11 11:19 jeckels
Related45735»45540, 45735