Another Jetty Web Server issue

[mlcarson]

Lots of issues with the web server.
Software Version: SageTV V9.0.7.369
Java Version: 1.7.0_79
Operating System: Windows 8 6.2 (ie Windows 10 64-bit)
Current STV File: SageTV7.xml (version 9.0.1.1 10/13/2015)

This all started out with just trying to get the BMT Metadata Scan to work. It does work for me now but then noticed all of the web stuff along the way. I installed the full Phoenix UI plugin and also tried just the Phoenix Core Services.

http://localhost:8080

Error 404 - Not Found.
No context on this server matched or handled this request.
Contexts known to this server are: •/ ---> org.mortbay.jetty.handler.ContextHandler@11a8af7{/,file:/C:/Program%20Files%20(x86)/SageTV/SageTV/jetty/static/}
•/apps ---> org.mortbay.jetty.webapp.WebAppContext@187e120{/apps,C:\Program Files (x86)\SageTV\SageTV\jetty/webapps/apps.war}
•/bmt ---> org.mortbay.jetty.webapp.WebAppContext@8f8a71{/bmt,C:\Program Files (x86)\SageTV\SageTV\jetty/webapps/bmt.war}

http://localhost:8080/apps
This brings up a nice Web Applications page with a single entry:
Batch Metadata Tools - Web Interface
Jetty Web Server Plugin Version 2.3.0.14
Jetty Web Server Version 6.1.19

Clicking this menu item gives:
http://localhost:8080/bmt
HTTP ERROR: 503

Problem accessing /bmt. Reason:
SERVICE_UNAVAILABLE


Creating the index.html file listed in the other thread gives a nice little menu for the base website. http://localhost:8080
Sage Web Server
Mobile

Web Remote

Both Mobile and Web Remote menus don't work though.
Mobile:
http://localhost:8080/sagem/m/menu.jsp
HTTP ERROR: 404

Problem accessing /sagem/m/menu.jsp. Reason:
NOT_FOUND

Web Remote:
http://localhost:8080/sagem/m/webrem...OCESS_LOCAL_UI
HTTP ERROR: 404

Problem accessing /sagem/m/webremote.jsp. Reason:
NOT_FOUND

I also ran into the x-vfs.xml issue and updated that with the following URL contents which eliminated some other issues.
https://raw.githubusercontent.com/st.../vfs/x-vfs.xml

No idea what's really going on with the web server but figure it's probably something easily fixed if you know what you're doing.

[Korny]

I know with my install BMT was broken until I used java 1.8 after the last update using ubuntu. Your first error is normal when connecting to jetty. 1.8 does break /apps though

[stuckless]

That html snippet that I posted was mainly for mainly for people that are running java 1.8 and the /apps no longer works. It has some static links for apps that "might" exist if you've installed them. And in your case, you haven't installed them, so, they are not there, and results in 404 errors.

The BMT issue could be the fact that the the newer BMT update is built using java 1.8 and as such, requires Java 1.8.