Jetty Web Server Issue

[Ghildebr]

Does anyone with java experience know what this means? I have the Jetty Web Server, version 2.3.0.14 installed on my Version 9 SageTV system. When I try and go to http://<server>:<port>/sage/Home I get this error:

HTTP ERROR: 404

Problem accessing /sage/Home. Reason:

NOT_FOUND
Powered by Jetty://


When I go to http://<server>:<port>/apps I get the below:

HTTP ERROR 500

Problem accessing /apps/. Reason:

PWC6033: Unable to compile class for JSP

PWC6199: Generated servlet error:
The type java.util.Comparator cannot be resolved. It is indirectly referenced from required .class files

Caused by:

org.apache.jasper.JasperException: PWC6033: Unable to compile class for JSP

PWC6199: Generated servlet error:
The type java.util.Comparator cannot be resolved. It is indirectly referenced from required .class files


at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:123)
at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:296)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:376)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:437)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:608)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:360)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:334)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
at org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:493)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:131)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:387)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)
Powered by Jetty://

I have tried to uninstall/reinstall the plugin but get the same results.
thanks,
Gary

[alfi33]

Are you using Java 8?

[Ghildebr]

Yes. But I know this has worked it the past with Java 8. At least I believe it has. What version of Java is supported?

[Ghildebr]

I stopped all Sage services and installed jre-7u79-windows-i586.exe and that made no differences. It was a good thought.

[stuckless]

Originally Posted by Ghildebr

I stopped all Sage services and installed jre-7u79-windows-i586.exe and that made no differences. It was a good thought.

Are you sure that Sage is running under Java 7... ie, did you completely remove Java 8? This is common and well known issue with Java 8 and sage. Under java 8 you can still run the webserver, though, if you go to /sage/ just the "apps" path has issues.

[Ghildebr]

I stopped all sage services, extenders, and clients. Went to "Programs and Features" and completely removed Java 8. Then I did a fresh install of Java 7. Is this not correct?

[alfi33]

Originally Posted by Ghildebr

I stopped all sage services, extenders, and clients. Went to "Programs and Features" and completely removed Java 8. Then I did a fresh install of Java 7. Is this not correct?

I think that's how you'd want to do it...so not sure. I do know that I get that exact same error message when I go to /apps/ with Java8.

[Ghildebr]

Originally Posted by alfi33

I think that's how you'd want to do it...so not sure. I do know that I get that exact same error message when I go to /apps/ with Java8.

Does the web page display correctly when you go to http://<server>:<port>/sage/Home?

This worked in the recent past. I am sure of it. This is how I checked to see if anyone was using Sage to watch anything. That way I knew if I could do maintenance on the server.

[alfi33]

Originally Posted by Ghildebr

Does the web page display correctly when you go to http://<server>:<port>/sage/Home?

Yeh, that works fine for me with Java 8.

Do you have any of the other web apps installed? Such as:
http://<server>:<port>/sagem/m/ or http://<server>:<port>/bmt/
Do any of these work?

[Ghildebr]

Originally Posted by alfi33

Yeh, that works fine for me with Java 8.

Do you have any of the other web apps installed? Such as:
http://<server>:<port>/sagem/m/ or http://<server>:<port>/bmt/
Do any of these work?

Both of those give the same error.

HTTP ERROR: 404

Problem accessing /bmt/. Reason:

NOT_FOUND
Powered by Jetty://

[Ghildebr]

Do you know what the path is on the C:\ drive for "/sage/Home"? The error is "NOT_FOUND". I would like to see if anything is in that location.

[alfi33]

Originally Posted by Ghildebr

Do you know what the path is on the C:\ drive for "/sage/Home"? The error is "NOT_FOUND". I would like to see if anything is in that location.

I think that goes here, but not certain:
C:\Program Files (x86)\SageTV\SageTV\jetty\webapps\nielm_sagewebserver\webapp\index.html

Did you try reinstalling the Jetty Web Server....or just the Web Interface?

[dstanley]

Ghildebr

What OS are you running?
Is it possible the firewall is blocking it?
Windows 10 upgrades sometimes installs a webserver and takes away the computers ability to host a server. I have seen this issue on Windows 10 installs and you can remove it like this:
Run appwiz.cpl use Turn Windows features on or off and uninstall any web management tools.

[Ghildebr]

This is on a Server 2012 R2 in a Domain. The windows firewall is off. I have ran in this type of configuration for years. Prior to Server 2012 R2 I was using Server 2008 R2. This is a headless box. No video is ever watched on the box itself. It runs a max of 4 hd300's, 3 clients and 5 placeshifter clients. Twice I have had all clients running as a test and the server is able to keep up. (Server Specs, HP Proliant ML350 G9, 2 Xeon processors with 32 cores, 64 Gb memory, 8 drive RAID set with 10k drives).

I believe I have found the issue but I do not know how to fix it without a complete uninstall/reinstall of SageTV. I have already tried to uninstall all plugins and then reinstall but that did not work. Where I believe I went wrong was I have this set to run as a service. Somehow I checked "Enable Service Recovery" and when I thought I had things shut down to upgrade Java the service on the server started during the middle of a Java upgrade.

This is a very old plugin and doesn't look like anyone is left to assist with troubleshooting. I primarily use the web client to determine if anyone is connected to the server to see if I can do maintenance on the box. There looks to be a newer web plugin in development. I may need to cut my losses and look at the new plugin. I just have to find the time to work on it.

[Ghildebr]

Well, just because I could, I completely uninstalled and reinstalled all the plugins again (3rd time). This time I did it from the console of the server and not a placeshifter client connecting to the server. I did the exact same procedure all three times. I am not exactly sure why this time it worked.

I am on the latest version 8 Java with all of my plugins installed and the web interface works, just like it has for many, many, years.

All is right in the world.

[BobbyDing]

So is it correct that I get the page/error (below) when I select the WebUI for the SageTV Docker container? I did find that two of these links do work. I just want to be sure that this is what I should see.

Thanks


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@f2c58a4{/,file:/opt/sagetv/server/jetty/static}
/sage ---> org.mortbay.jetty.webapp.WebAppConte...ewebserver.war}
/apps ---> org.mortbay.jetty.webapp.WebAppConte...bapps/apps.war}
/sagex ---> org.mortbay.jetty.servlet.Context@38b442df{/sagex,null}
/bmt ---> org.mortbay.jetty.webapp.WebAppConte...ebapps/bmt.war}
.
.

[stuckless]

Originally Posted by BobbyDing

So is it correct that I get the page/error (below) when I select the WebUI for the SageTV Docker container? I did find that two of these links do work. I just want to be sure that this is what I should see.

Thanks


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@f2c58a4{/,file:/opt/sagetv/server/jetty/static}
/sage ---> org.mortbay.jetty.webapp.WebAppConte...ewebserver.war}
/apps ---> org.mortbay.jetty.webapp.WebAppConte...bapps/apps.war}
/sagex ---> org.mortbay.jetty.servlet.Context@38b442df{/sagex,null}
/bmt ---> org.mortbay.jetty.webapp.WebAppConte...ebapps/bmt.war}
.
.

Pretty much... since the "apps" doesn't work, I go to the root of the server which gives an error, but at least, it shows the paths that are valid... so you can click on "/sage" to get to the webserver or "/bmt" to get to BMT, etc.

[anotherhaus]

For those getting the 404 error on the web server home page (:8080/) with:

Error 404 - Not Found.

No context on this server matched or handled this request.

followed by a list of contexts, go into c:\Program Files (x86)\SageTV\SageTV\jetty, create a folder called "static" (lowercase), and inside static create a file "index.html".

You can paste code like this into index.html and the web root will give you a nicely formatted list of contexts you link to or a meta refresh to a single page:

List of links:

<html>
<head>
Sage Web Server
</head>
<body>
<p><a href="/sagem/m/menu.jsp">Mobile</a></p>
<p><a href="/sagem/m/webremote.jsp?context=SAGETV_PROCESS_LOCAL_UI">Web Remote</a></p>
</body>
</html>

Instant refresh directly to mobile view:

<html>
<head>
<meta http-equiv="refresh" content="0;url=/sagem/m/menu.jsp" />
</head>
<body>
<p><a href="/sagem/m/menu.jsp">Mobile</a></p>
</body>
</html>

Pardon if work on this is already happening; I've been searching and didn't come across anything yet.