Java 8 ?

[odledm]

I was running Java 8 on my Sage TV server pc and had some problems with a spinning wheel appearing and locking up my extenders. I recently downgraded to Java 7 (32-bit) and things seem to be working better (I no longer see the lockups on my extender, but it has only be a couple of days). I never had issues with the webserver not working and on the surface everything looked to be working at first (with Java 8). The MyMovies plugin was behaving a little flakey (with Java 8). I realize I'm not offering much detail in some of these descriptions, but thought I would throw it out there anyway. I hope it helps.

[nyplayer]

Originally Posted by odledm

I was running Java 8 on my Sage TV server pc and had some problems with a spinning wheel appearing and locking up my extenders. I recently downgraded to Java 7 (32-bit) and things seem to be working better (I no longer see the lockups on my extender, but it has only be a couple of days). I never had issues with the webserver not working and on the surface everything looked to be working at first (with Java 8). The MyMovies plugin was behaving a little flakey (with Java 8). I realize I'm not offering much detail in some of these descriptions, but thought I would throw it out there anyway. I hope it helps.

Have to disagree with you thr WebSERVER does not work with Java 8. Did you Install Java 8 32 bit as Sagetv only uses Java 8 32 bit.
http://forums.sagetv.com/forums/show...=48458&page=16

[odledm]

I am pretty sure that I installed both the 64-bit and 32-bit versions of Java 8 but it is possible that I only installed the 64-bit version (it is a new machine and I have slept a few times since then, I can check tonight when I get home as I should still have the download ). I saw your previous post so I was surprised that mine was "working". By working, I mean that I was able to login to each of the plugin webapps that I had including the mobile web and BMT. There was obviously something on my system that wasn't working properly as it seems to be behaving much better when I installed Java 7 32-bit. I saw a post (I think it was by you) suggesting just installing the 32-bit version of Java 7 if there was a desire to also have the 64-bit of Java 8 running and went with that strategy.

[nyplayer]

Originally Posted by odledm

I am pretty sure that I installed both the 64-bit and 32-bit versions of Java 8 but it is possible that I only installed the 64-bit version (it is a new machine and I have slept a few times since then, I can check tonight when I get home as I should still have the download ). I saw your previous post so I was surprised that mine was "working". By working, I mean that I was able to login to each of the plugin webapps that I had including the mobile web and BMT. There was obviously something on my system that wasn't working properly as it seems to be behaving much better when I installed Java 7 32-bit. I saw a post (I think it was by you) suggesting just installing the 32-bit version of Java 7 if there was a desire to also have the 64-bit of Java 8 running and went with that strategy.

That is the Strategy I went with ... I downloaded the Java 7 32 bit off line Install and backed it up just in case Java 7 completely goes away.

[odledm]

So I double checked this weekend and it looks like I only had installed the 64-bit version of Java 8 before so that may be why my systems was mostly working before. Having Java 7 32-bit with Java 8 64-bit still seems to be working well for me.

[dinki]

Originally Posted by JerryB

Thanks. If you can fix it, great; if not, no problem since I can always reload java 7. Here is the error message:

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)

I'm getting this same error message. Can someone tell me what I might need to do to fix this?

[nyplayer]

Java 8 and the Jetty Webserver do not get along if you want to keep the WebServer do not load up java 8.

[gary201]

Does anyone know whether there are any plans to resolve this?

[stuckless]

Originally Posted by gary201

Does anyone know whether there are any plans to resolve this?

There are plans... Just right now the Android MiniClient is consuming my time.

[wubdich]

I'm running Sage Webserver version 2.43 on Java 1.8.0_65 and Windows 8.1. Software Version is SageTV V9.0.3.173

[mdnttoker]

I'm running on JAVA 8 as well. Every once in awhile I have to go into the Jetty webserver settings and "restart" the webserver to get it to run, but otherwise seems to run just fine under 8.

I think the PLEX sage addin still has issues with JAVA 8 though if you are running PLEX.

[Fuzzy]

The issue isn't with Jetty specifically, but some of the web based plugins for sage, via sagex, do not work on every function with Java 8.

[FriscoJohn]

Finally updated my Win7 machine to Java8 because of all the warnings about the dangers of leaving an old version of Java (mine was 1.6) on your computer. Then when I tried to run SageTV I got the dreaded errors:

"msvcr.dll missing"
and
"Could not find jvm.dll. Please install Java Runtime Environment 1.4"

I spent a few hours trying to figure this out--looking for weird registry entries left over from the old Java install and stuff. I finally did the obvious thing and searched this board for "Updating Java". Found this post by Opus4

http://forums.sagetv.com/forums/showthread.php?t=40521

which says that one has to install the MS Visual C++ 2010 Runtime to get the new Java to work.

Skeptical, I did this and to my surprise everything worked!

This is the last time I do anything to Sage without a thorough forum search.

Hope my experience will serve an example of how not to go about making changes to your Sage machine.

[Deacon Crusher]

Is there a list of which web apps require java 7 versus java 8?

And is there anything that can be done?

In particular Sage recording extender.

Should it work with Java 8?

If I got to

http://127.0.0.1:8080/sage/Home

I get a functioning nice interface.

If I go to

http://127.0.0.1:8080/apps

I get this

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

Thanks

Originally Posted by Fuzzy

The issue isn't with Jetty specifically, but some of the web based plugins for sage, via sagex, do not work on every function with Java 8.

[zzmystique]

Its been a long time since i have posted to the forum..
I get this same error for http://127.0.0.1:8080/apps but none of the other apps seem to be affected. Is there anything essential running under http://127.0.0.1:8080/apps that would be a good reason to revert back to Java 7.

Thanks

Originally Posted by Deacon Crusher

Is there a list of which web apps require java 7 versus java 8?

And is there anything that can be done?

In particular Sage recording extender.

Should it work with Java 8?

If I got to

http://127.0.0.1:8080/sage/Home

I get a functioning nice interface.

If I go to

http://127.0.0.1:8080/apps

I get this

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

Thanks

[egeller]

Somewhere in the Plugins Forum there is documentation on the work-around for the issue of Java 8 and the Webserver. It's not a big deal.

From memory, it involves creating a folder named "static" in the "jetty" folder. Then you create a file, named "index.html", as your landing page, and put it in the "static" folder. You can write HTML to link to the SageTV web page on your network or do whatever you want. You should then be able to access the page with the url http://server-or-ip:8080 .

I recall there were some initial suggestions on what to put in the html file. However, I've customized the crap out of mine and have links to the SageTV server web page, Couchpotato, Sickbeard, Plex, BMT and a couple of Ceton diagnostic web pages I created to track tuner temp and status.