Plugin: Mobile Web UI for v7

[darcilicious]

Okay, I did the jetty upgrade and restarted SageTV when prompted. Then I upgraded the Mobile Web App but should the version number at the bottom of the web pages say v1.2 or v1.3 after updating?

Mine still say v1.2...

Edit: Okay, found a post above with similar issue; I'll look at / post my jar files shortly.

Edit again: and then I read some more

Right, I'm outta here. Enough updates for one day

Thanks again for all your work on this -- I rely on this app a lot and it's one of the main reasons I haven't switched to anything else from SageTV

[jreichen]

LOL. I'm trying to finish off some things for the Jetty plugin then I'll work on the web interfaces.

[jchong]

I performed a fresh install of SageTV 7 and installed the Mobile Web UI plugin but I'm having problems. When I visit the site (http://<host>:8080/sagem/m/menu.jsp)

I get the following error:



HTTP ERROR: 503

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

SERVICE_UNAVAILABLE

Powered by Jetty://


I have access to the following though:

http://<host>:8080/sage/Home
http://<host>:8080/bmt
http://<host>:8080/sjq
http://<host>:8080/sre

[jreichen]

Can you enable SageTV's debug logging, then enable Jetty's debug logging by changing the setting in the plugin manager for the Jetty plugin? Restart Jetty then try to access the page. After you get the error save off your debug log, zip it, post it here, and I'll take a look at it.

[jreichen]

You might also check out another related thread and see if that fixes your issue.

[ryttingm]

Originally Posted by jchong

I performed a fresh install of SageTV 7 and installed the Mobile Web UI plugin but I'm having problems. When I visit the site (http://<host>:8080/sagem/m/menu.jsp)

I get the following error:



HTTP ERROR: 503

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

SERVICE_UNAVAILABLE

Powered by Jetty://


I have access to the following though:

http://<host>:8080/sage/Home
http://<host>:8080/bmt
http://<host>:8080/sjq
http://<host>:8080/sre

I'm having the exact same problem. I can actually get to http://<host>:8080/sagem. Which just gives me the listing of that directory. The menju.jsp file is missing in my jetty/webapps/SageWebApp/webapp/m directory. I noticed the timestamp on the jetty/webapps/SageWebApp directory seems correct on 5/20. But I did notice that the timestamp on the jetty/contexts/sagewebapp.xml is still set to 4/4/2010. Is there supposed to be a menu.jsp file in jetty/webapps/SageWebApp/webapp/m?

-Mike

[Mark SS]

Exactly the same problem here. It worked when I initially installed it yesterday but isn't now. Changes since doing so are addition of bmt and Serenity theme.

Uninstalled and re-installed, problem remains. Have checked the jetty folder and the folder structure, css and images are there but no jsp files.

[jchong]

Originally Posted by jreichen

Can you enable SageTV's debug logging, then enable Jetty's debug logging by changing the setting in the plugin manager for the Jetty plugin? Restart Jetty then try to access the page. After you get the error save off your debug log, zip it, post it here, and I'll take a look at it.

Attached is a copy of the debug log (I set the Jetty logging to verbose).

[jreichen]

Originally Posted by ryttingm

I'm having the exact same problem. I can actually get to http://<host>:8080/sagem. Which just gives me the listing of that directory. The menju.jsp file is missing in my jetty/webapps/SageWebApp/webapp/m directory. I noticed the timestamp on the jetty/webapps/SageWebApp directory seems correct on 5/20. But I did notice that the timestamp on the jetty/contexts/sagewebapp.xml is still set to 4/4/2010. Is there supposed to be a menu.jsp file in jetty/webapps/SageWebApp/webapp/m?

-Mike

And what's the timestamp on the jetty/webapps/SageWebApp.war file?

[ryttingm]

Originally Posted by jreichen

And what's the timestamp on the jetty/webapps/SageWebApp.war file?

4/4/2010

[robogeek]

I'll chime in and say that after installing SageTV v7 on WHS and installing Jetty and the web interfaces, I also had an issue with the mobile web UI. After installing the mobile web UI, I tested it and everything worked as expected. After restarting SageTV, the SageWebApp wasn't being fully redeployed for some reason. I had to delete the SageWebApp directory to get it to redeploy.

The WHS version of SageTV has Java in the jre directory of the SageTV installation directory. I think it's an older Java 1.6 version. After installing Java 1.6 Update 20 from java.com and removing the SageTV\jre directory (all with SageTV shutdown), the .war seems to be deploying fine now when SageTV is restarted. Not sure if it was a Java thing with the older Java version included with SageTV or just a coincidence.

[Mark SS]

Doing the same worked for me. Stopped service, deleted SageWebApp, restarted, mobile interface now working again.

[jreichen]

Originally Posted by Mark SS

Doing the same worked for me. Stopped service, deleted SageWebApp, restarted, mobile interface now working again.

Great, thanks for the info. That sounds like the workaround for now.

Yesterday I discovered that Jetty holds on to an exception reference and doesn't print it out if a web app doesn't deploy properly. I'm working on an update that should be ready in a few days and am putting some code in to print out the exception, so if anyone can wait until then and get a debug log for me that would be great.

[jreichen]

Originally Posted by ryttingm

I'm having the exact same problem. I can actually get to http://<host>:8080/sagem. Which just gives me the listing of that directory. The menju.jsp file is missing in my jetty/webapps/SageWebApp/webapp/m directory. I noticed the timestamp on the jetty/webapps/SageWebApp directory seems correct on 5/20. But I did notice that the timestamp on the jetty/contexts/sagewebapp.xml is still set to 4/4/2010. Is there supposed to be a menu.jsp file in jetty/webapps/SageWebApp/webapp/m?

-Mike

Yes, and there should be a jetty/webapps/SageWebApp/jsp folder with .class files for each of the jsps. (When a jsp is requested, Java web servers convert it to a servlet and compile it.)

[jreichen]

Originally Posted by jchong

Attached is a copy of the debug log (I set the Jetty logging to verbose).

Thanks for the log but it doesn't have any Jetty debug messages. Did you restart Jetty after changing the log level?

[Mark SS]

Shortly after posting, I restarted Sage and the same thing happened again. Had to repeat the stop/start/delete to get it back again.

[jchong]

Originally Posted by jreichen

Thanks for the log but it doesn't have any Jetty debug messages. Did you restart Jetty after changing the log level?

I thought I did... I'll try creating a new log and will post it again.

[jchong]

I've attached another log - this time I rebooted the server after making each changes so it should have the details you need.

There are two sets of logs:

sagetv_0.txt and sagetvclient_0.txt I had the Jetty log set to DEBUG

sagetv_1.txt and sagetvclient_1.txt I had the Jetty log set to VERBOSE


I refreshed the following URL's several times (and tried with multiple browsers - Firefox/Chrome):

http://<host>:8080/sagem/m/menu.jsp
http://<host>:8080/sagem/m/
http://<host>:8080/sagem/

I took a quick look at the logs and I'm not sure anything related to the URL's above was logged (I searched for menu.jsp and sagem). Anyway, hopefully you find the details you were looking for.

FYI: this was a clean install of SageTV 7 except for my wiz.bin file which was copied over from SageTV 6

[voorhees]

Originally Posted by robogeek

I'll chime in and say that after installing SageTV v7 on WHS and installing Jetty and the web interfaces, I also had an issue with the mobile web UI. After installing the mobile web UI, I tested it and everything worked as expected. After restarting SageTV, the SageWebApp wasn't being fully redeployed for some reason. I had to delete the SageWebApp directory to get it to redeploy.

The WHS version of SageTV has Java in the jre directory of the SageTV installation directory. I think it's an older Java 1.6 version. After installing Java 1.6 Update 20 from java.com and removing the SageTV\jre directory (all with SageTV shutdown), the .war seems to be deploying fine now when SageTV is restarted. Not sure if it was a Java thing with the older Java version included with SageTV or just a coincidence.

robogeek, thanks so much for the info. I had been playing around with this for a week now. Started with a clean install of v7, but never got all of the files to deploy in the directories so the Mobile Web App never worked on the new install. I did both of your suggestions, and it works like a champ again. The Mobile Web App deployed correctly and all is well. Thanks again for the pointers. Much appreciated.

[jreichen]

jchong,

I released version 2.0 of the Jetty plugin last night. If an exception occurs when a webapp is starting, Jetty stores a reference to it but doesn't print it to the log. I added a fix to the plugin to check for that exception and print it. Would you mind creating those logs again?