10.32.65.141 - - [13/Jun/2017:00:00:00 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:02 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
We're trying to understand what's trying to invoke the jsp.
A few facts
- 10.32.65.141 is the web server where IIS is installed - we presume this is therefore the requestor?
The missing appstatus.jsp has been deliberately renamed as it was causing other errors and is no longer needed to run.
There are no Ebase scheduled jobs invoking this
We can't see any windows scheduled jobs invoking this (not 100% sure of this)
The entries are only in log files of the Internal production Tomcat system