Plugin: Mobile Web UI for v7

[jchong]

Here's the log I created after installing Jetty version 2.0. Jetty logging was set to VERBOSE and DEBUG for SageTV was turned on before I rebooted the server.

When I first installed Jetty 2.0 I was able to see this page:

http://<host>:8080/apps/

After rebooting, I only see a directory listing of files:

SageLogo256small.png
apps.css
favicon.ico

The Mobile Web UI is giving a 404 error now when I try to access:

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

The following pages work fine:

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

[jreichen]

That's strange, I don't even see INFO level logging for Jetty in your logs. I do see it on my server. Can you post all the properties in Sage.properties that begin with 'jetty/'?

[robogeek]

Originally Posted by robogeek

Not sure if it was a Java thing with the older Java version included with SageTV or just a coincidence.

The Java upgrade must have been a coincidence. After updating to the Jetty 2.0 web server, both the apps and SageWebApp folders weren't completely deployed after restarting SageTV. Deleting those directories from jetty\webapps and restarting the Jetty web server from the SageTV Plugin Manager allowed both to deploy correctly.

Not sure if it matters, but I'm running SageTV v7 for WHS and I have removed the default Java installation that installed with the WHS version of SageTV and installed the latest Java v1.6 update 20 from java.com. I'll have to enable my debug logging and do some more testing.

[jchong]

Originally Posted by jreichen

That's strange, I don't even see INFO level logging for Jetty in your logs. I do see it on my server. Can you post all the properties in Sage.properties that begin with 'jetty/'?

Below are all the lines that begin with jetty/

Please note that I've changed the log level back to INFO. If you want, I can set it back to DEBUG or VERBOSE and run this again (after restarting SageTV).

-----

jetty/jetty.configfiles="C\:\\Program Files\\SageTV\\SageTV\\jetty\\etc\\jetty.xml"
jetty/jetty.home=C\:\\Program Files\\SageTV\\SageTV\\jetty
jetty/jetty.log.level=INFO
jetty/jetty.logs=C\:\\Program Files\\SageTV\\SageTV\\jetty\\logs
jetty/jetty.port=8080
jetty/jetty.ssl.port=8443
jetty/upnp=Manual Configuration
jetty/upnp.external.http=8080
jetty/upnp.external.https=8443

[jreichen]

Your properties look fine. I'm not sure why the logging isn't showing up. Stuckless posted a utility the other day to clean up the JARs folder. You might check that out. I noticed in your log that you have a xerces.jar in your classpath and that has been know to create problems for some users (not necessarily for the mobile web ui, though).

[jchong]

I ran the utility that Stuckless posted (while SageTV was disabled) and it didn't make a difference.

How do I get rid of xerces.jar? I searched and didn't find any file with that name.

[jreichen]

Originally Posted by jchong

I ran the utility that Stuckless posted (while SageTV was disabled) and it didn't make a difference.

How do I get rid of xerces.jar? I searched and didn't find any file with that name.

Your log file says it's at C:\Program Files\SageTV\SageTV\xerces.jar. Shut down Sage, copy the file to a backup location outside the SageTV folder, then start Sage again.

[jchong]

Originally Posted by jreichen

Your log file says it's at C:\Program Files\SageTV\SageTV\xerces.jar. Shut down Sage, copy the file to a backup location outside the SageTV folder, then start Sage again.

I've checked my system - no such file exists. Could that be the cause of the problem? Should I find a copy of xerces.jar and place it into the SageTV installation folder?

[jreichen]

From what I read you don't want xerces.jar so it's good that it's not on your machine. AFAIK the fact that it's in the classpath won't hurt anything. Java will just ignore it if the file doesn't exist.

[GKusnick]

FYI, menu.jsp contains a hard-coded path for jetty/webapps/SageWebApp/webapp/WEB-INF/mobile_menu.json, which basically breaks the app if you try to deploy it to some other directory.

[jreichen]

Please see the Jetty 2.0 support thread for information about an update to 2.0.1.

[jchong]

Installing Jetty v2.0.1 resolved the problem I had with the /apps page but the Mobile Web UI still doesn't work after a restart - I'm getting the following error:

HTTP ERROR: 503
Problem accessing /sagem/m/menu.jsp. Reason:
SERVICE_UNAVAILABLE
Powered by Jetty://


I'm wondering if I should just start with a fresh install (of Windows and SageTV)...

[jreichen]

Did you delete the jetty/webapps/SageWebApp directory manually? Make sure Sage is shut down when you do. This needs to be done once after you update to 2.0.1.

Also check your log files again and make sure there's nothing in there. I wouldn't expect this error after you do the above so if there's another problem I'd like to see what's in the logs.

[jreichen]

Version 1.4.0 has been released and can be installed from the SageTV Plugin Manager. Changes include:

1. View what's playing on SageTV Clients from the home page
2. Favorite Automatic Conversions
3. Adopt conventions for /apps application
4. Regenerated tag library for SageTV v7 API
5. Don't hard-code resource path of mobile_menu.json
6. Close mobile_menu.json file reader
7. Convert end-of-line characters from LF (Linux) to CRLF (Windows) for the /apps files.
8. Increase maximum for Favorite Keep at Most from 15 to 63
9. Remember last values for video conversions

Jason

[phelme]

i'm getting this error as well:

Message: C:\Program%20Files\SageTV\SageTV\jetty\webapps\SageWebApp\webapp\WEB-INF\mobile_menu.json (The system cannot find the path specified)

Page Generated Sat Jul 17 12:39:49 PDT 2010

SageTV Mobile Web Interface Version 1.3.1


it's trying to access this page: http://127.0.0.1:8090/sagem/m/menu.jsp

my Jetty info:
Jetty Web Server Plugin Version 2.0.1.19
Jetty Web Server Version 6.1.19

My Path: C:\Program Files\SageTV\SageTV\jetty\webapps\SageWebApp\webapp\WEB-INF -- mobile_menu.json is in there. I shutdown Sage, deleted the SageWebApp directory and let it be rebuilt too.


and a snippet from the Jetty logs:

127.0.0.1 - - [17/Jul/2010:20:10:16 +0000] "GET /sjq/SJQ?proto=4&cmd=pop HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 - - [17/Jul/2010:20:11:29 +0000] "GET /sagem/m/menu.jsp HTTP/1.1" 401 1387 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)"
127.0.0.1 - sage [17/Jul/2010:20:11:31 +0000] "GET /sagem/m/menu.jsp HTTP/1.1" 500 1733 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)"
127.0.0.1 - sage [17/Jul/2010:20:11:31 +0000] "GET /sagem/m/css/sage_mobile.css HTTP/1.1" 200 2047 "http://127.0.0.1:8090/sagem/m/menu.jsp" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)"
127.0.0.1 - - [17/Jul/2010:20:11:31 +0000] "GET /sagem/images/SageLogo256smallbluethird.png HTTP/1.1" 401 1413 "http://127.0.0.1:8090/sagem/m/menu.jsp" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)"
127.0.0.1 - - [17/Jul/2010:20:11:31 +0000] "GET /sagem/images/MarkerSysAlert2.png HTTP/1.1" 401 1403 "http://127.0.0.1:8090/sagem/m/menu.jsp" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)"
127.0.0.1 - - [17/Jul/2010:20:11:31 +0000] "GET /sagem/favicon.ico HTTP/1.1" 401 1388 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)"
127.0.0.1 - sage [17/Jul/2010:20:11:31 +0000] "GET /sagem/images/SageLogo256smallbluethird.png HTTP/1.1" 200 4763 "http://127.0.0.1:8090/sagem/m/menu.jsp" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)"
127.0.0.1 - sage [17/Jul/2010:20:11:31 +0000] "GET /sagem/images/MarkerSysAlert2.png HTTP/1.1" 200 2245 "http://127.0.0.1:8090/sagem/m/menu.jsp" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)"
127.0.0.1 - sage [17/Jul/2010:20:11:31 +0000] "GET /sagem/favicon.ico HTTP/1.1" 200 1367 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)"

---

Everything else under Jetty works: SageTV Web Interface, SJQ, bmt etc.

One odd thing is the version listed in the error, where is Interface Version 1.3.1 coming from when I've installed (and uninstalled and reinstalled) 1.4.0.21 via the plug-in mechanism?

[MitchSchaft]

Thanks for the update, mine is working fine!

[Brent]

I upgraded & am getting this message:

Message: C:\Program%20Files\SageTV\SageTV\jetty\webapps\SageWebApp\webapp\WEB-INF\mobile_menu.json (The system cannot find the path specified)

Haven't used the mobile web app for a while so not sure if I might be missing something from a past update.

[darcilicious]

Originally Posted by phelme

i'm getting this error as well:

[I]Message: C:\Program%20Files\SageTV\SageTV\jetty\webapps\SageWebApp\webapp\WEB-INF\mobile_menu.json (The system cannot find the path specified)

[...]

Wow, I have a draft post of the exact same issue. You just beat me to it

[saltlyck2]

Originally Posted by darcilicious

Wow, I have a draft post of the exact same issue. You just beat me to it

+1

[jreichen]

I wonder if it's the space in the path. I'm using Linux without a problem.