Strange problem with the SageTV Jetty webserver, always returns 404

[hagur]

Hi,

Are these forums still active?

Anyways, I'm running SageTV 7 and I had enabled the Jetty web server and the mobile web interface and everything was going smoothly. I rarely used the web interface, just wanted to have it just in case I needed it. Then all of a sudden I notice that it's no longer working.

http://myhtpc:8080/apps/ always returns 404.

This is the exact message:

HTTP ERROR: 404

Problem accessing /apps/. Reason:

    NOT_FOUND
Powered by Jetty://

I spent a whole lot of time on it, I removed and reinstalled the Jetty server multiple times and I reinstalled SageTV but nothing worked. Eventually, I just gave up on it ....

... until now. I decided to give it a go again and see if I could get this to work.

I installed SageTV 7 on another machine I have at home, and activated the Jetty web server and installed the mobile web UI. Everything worked fine on that machine! So I copied the Jetty folder from that machine to my HTPC, restarted SageTV and tried again, still just gives me the same 404 error.

Then I started wondering .... what the H**** did I do (if anything) in the meantime which could have caused the Jetty server to stop working all of a sudden. Then I realized that I had installed the XmlTV plugin which involved some messing around with import paths and what not. That's probably when the Jetty web server stopped working.

So now I've enabled the SageTV debug log on both machines and also set the Jetty log to VERBOSE.

After carefully comparing the logs on both machines, I can see that there is an error occurring on the HTPC machine which is not occuring on the other machine. It seems to have something to do with the xerces XML parser, which is one of the things I had to mess around with to get the XmlTV plugin working.

Here's a snippet from the log on the HTPC machine, where Jetty is not working:

mán. 10/31 21:06:02.363 [SageTV@1ad086a] ::DEBUG: started CompressingFilter
mán. 10/31 21:06:02.363 [SageTV@1ad086a] ::DEBUG: loaded class org.apache.jasper.servlet.JspServlet from sun.misc.Launcher$AppClassLoader@7d772e
mán. 10/31 21:06:02.363 [SageTV@1ad086a] ::DEBUG: Holding class org.apache.jasper.servlet.JspServlet
mán. 10/31 21:06:02.364 [SageTV@1ad086a] ::DEBUG: getResource(META-INF/services/javax.xml.parsers.DocumentBuilderFactory)=jar:file:/C:/Program%20Files/Java/jre6/lib/ext/xerces.jar!/META-INF/services/javax.xml.parsers.DocumentBuilderFactory
mán. 10/31 21:06:02.364 [SageTV@1ad086a] ::DEBUG: loaded class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl from sun.misc.Launcher$ExtClassLoader@11b86e7
mán. 10/31 21:06:02.365 [SageTV@1ad086a] ::WARN:  failed jsp
mán. 10/31 21:06:02.366 [SageTV@1ad086a] ::DEBUG: EXCEPTION 
mán. 10/31 21:06:02.366 [SageTV@1ad086a] ::DEBUG: loaded class org.mortbay.jetty.servlet.DefaultServlet
mán. 10/31 21:06:02.366 [SageTV@1ad086a] ::DEBUG: loaded class org.mortbay.jetty.servlet.DefaultServlet from sun.misc.Launcher$AppClassLoader@7d772e
mán. 10/31 21:06:02.367 [SageTV@1ad086a] ::DEBUG: Holding class org.mortbay.jetty.servlet.DefaultServlet
mán. 10/31 21:06:02.367 [SageTV@1ad086a] ::DEBUG: started org.mortbay.jetty.servlet.DefaultServlet$NIOResourceCache@1f2af1c
mán. 10/31 21:06:02.367 [SageTV@1ad086a] ::DEBUG: started org.mortbay.jetty.ResourceCache@1c6866d
mán. 10/31 21:06:02.367 [SageTV@1ad086a] ::DEBUG: resource base = file:/C:/Program%20Files/SageTV/SageTV/jetty/webapps/apps/webapp/
mán. 10/31 21:06:02.367 [SageTV@1ad086a] ::DEBUG: started default
mán. 10/31 21:06:02.367 [SageTV@1ad086a] ::WARN:  failed org.mortbay.jetty.webapp.WebAppContext@19ea173{/apps,C:\Program Files\SageTV\SageTV\jetty/webapps/apps.war}

Notice the Failed jsp part ? Must have got something to do with this?

The exact same line on the other machine (where Jetty is working):

mán. 10/31 21:16:12.882 [SageTV@118f375] ::DEBUG: started jsp

jsp starts fine there.

Any help would be greatly appreciated !

[hagur]

Ok ... I'm a little bit closer to the problem, and it is indeed related to the xerces parser.

On the HTPC (where jetty is not working), I had put xerces.jar into the lib/ext folder, (Program Files\Java\jre6\lib\ext)

I removed the file, restarted SageTV and now everything is working correctly! But I assume the XmlTv plugin is not, since it depends on the xerces parser.

How can I resolve this?

[cat6man]

i don't have an answer for you, but i had a 404 problem with SRE web access a while ago (see SRE3 thread)..............it also seemed correlated with the occurrence of excessively high java heap usage.

i rebooted, the java heap usage went back to normal, but eventually went high again. i rebooted again, and it stayed low/normal since.

i can't look at anything now though as we have been without power since saturday.............so sagetv is hibernating (literally)

[hagur]

Thanks for you input.

So my problem is that the xmltv plugin requires the xerces parser, but including it in the classpath causes jetty to fail to serve .jsp pages.

Anyone running xmltv AND jetty/web/mobile interface at the same time?? If so, what version of xerces are you running ?

Really need some help here ....