Plugin: Mobile Web Interface 1.2

[craigdthom]

Originally Posted by jreichen

Can you make sure the files are extracted to the right place? Under the SageTV folder, go into the jetty folder. From there, there should be a contexts folder with sagewebapp.xml and a webapps folder with SageWebApp.war and a SageWebApp folder (that contains the contents extracted from the war file)....

As best as I could tell ... the files and folder are in the correct place.
I have posted the jetty log file and attached the SAGE debug log

 127.0.0.1 -  -  [09/Dec/2008:15:27:49 +0000] "GET /sage/m/menu.jsp HTTP/1.1" 401 1407 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.4.154.29 Safari/525.19"
127.0.0.1 - sage [09/Dec/2008:15:27:51 +0000] "GET /sage/m/menu.jsp HTTP/1.1" 404 1401 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.4.154.29 Safari/525.19"
127.0.0.1 -  -  [09/Dec/2008:15:28:55 +0000] "GET /sage/m HTTP/1.1" 401 1398 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.4.154.29 Safari/525.19"
127.0.0.1 - sage [09/Dec/2008:15:28:55 +0000] "GET /sage/m HTTP/1.1" 302 0 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.4.154.29 Safari/525.19"
127.0.0.1 -  -  [09/Dec/2008:15:28:55 +0000] "GET /sage/m/ HTTP/1.1" 401 1399 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.4.154.29 Safari/525.19"
127.0.0.1 - sage [09/Dec/2008:15:28:55 +0000] "GET /sage/m/ HTTP/1.1" 200 323 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.4.154.29 Safari/525.19"
127.0.0.1 -  -  [09/Dec/2008:15:29:05 +0000] "GET /sage/m/ HTTP/1.1" 401 1399 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
127.0.0.1 - sage [09/Dec/2008:15:29:14 +0000] "GET /sage/m/ HTTP/1.1" 200 323 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
127.0.0.1 -  -  [09/Dec/2008:15:29:17 +0000] "GET /favicon.ico HTTP/1.1" 404 1298 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"

[jreichen]

That looks like debug logging from the Sage core. There isn't much information in there related to Jetty. Can you disable the debug logging in Sage.properties and enable it in JettyStarter.properties? To enable it in JettyStarter.properties, uncomment the DEBUG=true line and restart SageTV. That will give me more information about what Jetty is doing.

Thanks,
Jason

[Sparhawk6]

jreichen, I'm getting a weird error. The plugin was working just fine up until today, when I tried to record a basketball game. When I press record, I get this message:



I tried resetting the sage server, but it didn't do anything.

[craigdthom]

@ jreichen ...
The code section was actually the log file from the log folder in the jetty directory. I have since disabled the debug logging in Sage.properties and the JettyStarter.properties was already enabled. SAGE has been stopped and restarted ... I have logged into the web interface using different browsers and the mobile phone ... they all give me the same thing. I have also "touched" the agewebapp.xml file several times as well.

I am not too familiar with the file structure, but from the URL it seems as if the "menu.jsp" file should be in the "m" directory.
C:\Program Files\SageTV\SageTV\jetty\webapps\SageWebApp\webapp\m

Inside the m directory there is only 1 folder and that is the css folder and the css folder has nothing in it.

There is also 1 other "m" directory and it has about 15 ".jspf" files
C:\Program Files\SageTV\SageTV\jetty\webapps\SageWebApp\webapp\WEB-INF\jspf\m


the most recent Jetty log file listed below

65.91.116.33 -  -  [11/Dec/2008:05:11:51 +0000] "GET /sage/m HTTP/1.1" 401 1398 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
65.91.116.33 -  -  [11/Dec/2008:05:13:04 +0000] "GET /sage/m HTTP/1.1" 401 1398 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
65.91.116.33 -  -  [11/Dec/2008:05:13:56 +0000] "GET /sage/m HTTP/1.1" 401 1398 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
65.91.116.33 -  -  [11/Dec/2008:05:15:37 +0000] "GET /sage/m HTTP/1.1" 401 1398 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
127.0.0.1 -  -  [11/Dec/2008:06:31:35 +0000] "GET /sage/m/menu.jsp HTTP/1.1" 401 1407 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.4.154.29 Safari/525.19"
127.0.0.1 - sage [11/Dec/2008:06:31:46 +0000] "GET /sage/m/menu.jsp HTTP/1.1" 404 1401 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.4.154.29 Safari/525.19"
127.0.0.1 -  -  [11/Dec/2008:06:31:59 +0000] "GET /sage/m/ HTTP/1.1" 401 1399 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.4.154.29 Safari/525.19"
127.0.0.1 - sage [11/Dec/2008:06:31:59 +0000] "GET /sage/m/ HTTP/1.1" 200 323 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.4.154.29 Safari/525.19"
127.0.0.1 -  -  [11/Dec/2008:06:33:30 +0000] "GET /sage/m/ HTTP/1.1" 401 1399 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
127.0.0.1 - sage [11/Dec/2008:06:33:33 +0000] "GET /sage/m/ HTTP/1.1" 200 323 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
127.0.0.1 -  -  [11/Dec/2008:06:33:36 +0000] "GET /favicon.ico HTTP/1.1" 404 1298 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
127.0.0.1 - sage [11/Dec/2008:06:33:46 +0000] "GET /sage/m/menu.jsp HTTP/1.1" 404 1401 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
127.0.0.1 - sage [11/Dec/2008:06:37:08 +0000] "GET /sage/m/home.jsp HTTP/1.1" 404 1401 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
127.0.0.1 -  -  [11/Dec/2008:06:37:27 +0000] "GET /sage/m/home.jsp HTTP/1.1" 401 1407 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.4.154.29 Safari/525.19"
127.0.0.1 - sage [11/Dec/2008:06:37:27 +0000] "GET /sage/m/home.jsp HTTP/1.1" 404 1401 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.4.154.29 Safari/525.19"
65.91.116.33 -  -  [11/Dec/2008:06:48:37 +0000] "GET /sage/m HTTP/1.1" 401 1398 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
65.91.116.33 - sage [11/Dec/2008:06:49:59 +0000] "GET /sage/m HTTP/1.1" 302 0 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
65.91.116.33 - sage [11/Dec/2008:06:50:01 +0000] "GET /sage/m/ HTTP/1.1" 200 323 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
127.0.0.1 -  -  [11/Dec/2008:06:59:53 +0000] "GET /sage/m HTTP/1.1" 401 1398 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
127.0.0.1 - sage [11/Dec/2008:06:59:53 +0000] "GET /sage/m HTTP/1.1" 302 0 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
127.0.0.1 - sage [11/Dec/2008:06:59:53 +0000] "GET /sage/m/ HTTP/1.1" 200 323 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
65.91.116.33 -  -  [11/Dec/2008:07:00:10 +0000] "GET /sage/m HTTP/1.1" 401 1398 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
65.91.116.33 - sage [11/Dec/2008:07:00:13 +0000] "GET /sage/m HTTP/1.1" 302 0 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
65.91.116.33 - sage [11/Dec/2008:07:00:15 +0000] "GET /sage/m/ HTTP/1.1" 200 323 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
65.91.116.33 -  -  [11/Dec/2008:07:02:34 +0000] "GET /sage/m HTTP/1.1" 401 1398 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
65.91.116.33 - sage [11/Dec/2008:07:02:38 +0000] "GET /sage/m HTTP/1.1" 302 0 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
65.91.116.33 - sage [11/Dec/2008:07:02:39 +0000] "GET /sage/m/ HTTP/1.1" 200 323 "-" "MOT-V3am/00.62 UP.Browser/6.2.3.4.c.1.123 (GUI) MMP/2.0"
127.0.0.1 -  -  [11/Dec/2008:07:03:39 +0000] "GET /sage/m HTTP/1.1" 401 1398 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
127.0.0.1 - sage [11/Dec/2008:07:03:42 +0000] "GET /sage/m HTTP/1.1" 302 0 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
127.0.0.1 - sage [11/Dec/2008:07:03:42 +0000] "GET /sage/m/ HTTP/1.1" 200 323 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
127.0.0.1 -  -  [11/Dec/2008:07:03:45 +0000] "GET /favicon.ico HTTP/1.1" 404 1298 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"

[jreichen]

Originally Posted by Sparhawk6

jreichen, I'm getting a weird error. The plugin was working just fine up until today, when I tried to record a basketball game. When I press record, I get this message:

I tried resetting the sage server, but it didn't do anything.

That's happening if the recording will cause a conflict. I'll have it fixed in the next update.

[jreichen]

Originally Posted by craigdthom

I am not too familiar with the file structure, but from the URL it seems as if the "menu.jsp" file should be in the "m" directory.
C:\Program Files\SageTV\SageTV\jetty\webapps\SageWebApp\webapp\m

Inside the m directory there is only 1 folder and that is the css folder and the css folder has nothing in it.

There is also 1 other "m" directory and it has about 15 ".jspf" files
C:\Program Files\SageTV\SageTV\jetty\webapps\SageWebApp\webapp\WEB-INF\jspf\m

It looks like Jetty didn't fully deploy the war file. Open the war file (it's in zip format) and make sure m/menu.jsp is in there (there's around 1000 files total). Then delete the C:\Program Files\SageTV\SageTV\jetty\webapps\SageWebApp folder and touch sagewebapp.xml again.

[archie658]

I've been trying to use your software, but it crashes:

HTTP ERROR: 500

org.apache.xerces.dom.DeferredDocumentImpl.setDocumentURI(Ljava/lang/String;)V

RequestURI=/sage/m/
Caused by:

java.lang.AbstractMethodError: org.apache.xerces.dom.DeferredDocumentImpl.setDocumentURI(Ljava/lang/String;)V
	at org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:226)
	at org.apache.jasper.compiler.JspConfig.processWebDotXml(JspConfig.java:123)
	at org.apache.jasper.compiler.JspConfig.init(JspConfig.java:295)
	at org.apache.jasper.compiler.JspConfig.findJspProperty(JspConfig.java:360)
	at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:141)
	at org.apache.jasper.compiler.Compiler.compile(Compiler.java:409)
	at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:592)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:344)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
	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:729)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:285)
	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
	at org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:463)
	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:487)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1097)
	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:129)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1088)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
	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:729)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.Server.handle(Server.java:324)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:829)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488)

Powered by Jetty://

I'm wondering why there's a mention of xerces (I'm/was using that for xmltv files).

[jreichen]

Java's handling of XML parsers has to be one of my least favorite features of the platform. It doesn't take much to run into problems. With that out of the way...

Here's what I think is happening: Jetty is parsing an xml configuration file in the mobile web app. Java's XML API has chosen to parse the XML with a xerces XML parser from somewhere in the classpath with which Jetty is not compatible.

These Java XML parser problems can be tricky to track down so let's start with something simple:

I've never used xmltv. I assume it comes with a xerces.jar? If you're not still using xmltv, try removing xerces.jar from the JARs folder and restart Sage. If you are using xmltv I'll have to do some research.

What version of Java are you running?

[craigdthom]

Originally Posted by jreichen

It looks like Jetty didn't fully deploy the war file. Open the war file (it's in zip format) and make sure m/menu.jsp is in there (there's around 1000 files total). Then delete the C:\Program Files\SageTV\SageTV\jetty\webapps\SageWebApp folder and touch sagewebapp.xml again.

Excellent .. I am up and working

Thanks

[craigdthom]

This is a great plugin with lots of potential

Looks like I am now having the same problem as Sparhawk6 noted .

Message: java.lang.Integer cannot be cast to java.lang.Long

(Java ver 6 update 7)

[jreichen]

Originally Posted by craigdthom

This is a great plugin with lots of potential

Feel free to share your ideas

Originally Posted by craigdthom

Looks like I am now having the same problem as Sparhawk6 noted .

Message: java.lang.Integer cannot be cast to java.lang.Long

(Java ver 6 update 7)

Thanks for the report. I'll be out of town most of the day Saturday and I'm leaving town for the week on Monday. I'll see if I can squeeze in an update on Sunday.

[archie658]

Originally Posted by jreichen

I've never used xmltv. I assume it comes with a xerces.jar? If you're not still using xmltv, try removing xerces.jar from the JARs folder and restart Sage. If you are using xmltv I'll have to do some research.

What version of Java are you running?

This goes way back to SageTV version 2. I've two servers now. This is the older one that still uses xmltv. I've actually put a lot of effort in creating a nearly complete EPG for DVB-C out of different sources recently; things were changed here in Holland.
I'm not sure if the version I'm now using needs the xerces.jar, because I've tried several in the past. BTW, Xerces is a generic xml toolkit: http://xml.apache.org).

But I've also a new server that doesn't use SBDARecorder and doesn't need xmltv anymore (it's using tvtv and the DVB-C tuner for the EPG). I will install your webserver on that one as well. I would love to see my servers on my phone . Can it be reversed proxied trough ssl? The original web server has some issues because it hardcodes the /sage/ path sometimes (after searches) and I need two remaps for my two servers.

I'm using the latest stable version of SageTV (6.4.8) on Java 6 Update 11 (on both servers now).

[archie658]

Update: It's working on the second server. Looks really nice! And even better, it can be reverse proxied through SSL, so it can be made secure as well. The image dir must also be redirected, but it doesn't conflict with webserver 2.22.

Why did you choose to make a search function for the recordings in stead of for the future airings? Recordings are already listed. I didn't get that part. And since there's such a nice Conversions page, I was looking for 'streaming' link as well .

Nice work!

[bcjenkins]

Can you describe the reverse proxy ssl setup?

Thanks!

B

[archie658]

Originally Posted by bcjenkins

Can you describe the reverse proxy ssl setup?

Somewhat simplified (I've two SageTV servers, but that has some problems);
This is for apache v2:

<VirtualHost 0.0.0.0:443>

    SSLEngine on
    SSLCertificateFile /etc/apache2/ssl.crt/server.crt
    SSLCertificateKeyFile /etc/apache2/ssl.key/server.key
    SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:!EXP:+eNULL
    SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0
    SSLVerifyClient none

    ProxyRequests Off
    ProxyTimeout 60
   # RewriteEngine on

    <Proxy *>
        AuthType Basic
        AuthName "Secure login"
        AuthUserFile /etc/apache2/passwd/passwd.httpd
        AuthGroupFile /etc/apache2/passwd/group.httpd
        Require Group admins
        Order Allow,Deny
        #Allow from 127.0.0.1 192.168.xx.0/24
        Allow from All
    </Proxy>

    ProxyPass /sage/m/ http://192.168.xx.xx:8081/sage/m/
    ProxyPass /sage/images/ http://192.168.xx.xx:8081/sage/images/
    ProxyPassReverse http://192.168.xx.xx:8081/sage/m/ https://192.168.yy.yy/sage/m/
    ProxyPassReverse http://192.168.xx.xx:8081/sage/images/ https://192.168.yy.yy/sage/images/

    ProxyPass /sage/ http://192.168.xx.xx:8080/sage/
    ProxyPassReverse http://192.168.xx.xx:8080/sage/ https://192.168.yy.yy/sage/
    ProxyPass /sagepublic/ http://192.168.xx.xx:8080/sagepublic/
    ProxyPassReverse http://192.168.xx.xx:8080/sagepublic/ https://192.168.yy.yy/sagepublic/
	
</VirtualHost>

192.168.xx.xx the SageTV server/interface
192.168.yy.yy the apache interface

The user/password for the proxy and for sage should be the same, if I remember correctly.

[matt91]

I just installed this plugin, but can't seem to get it to run correctly.

Here is what I have:

HTTP ERROR: 503

SERVICE_UNAVAILABLE
RequestURI=/sage/m/home.jsp
Powered by jetty://

Running webserver:

V2.22 21 Dec 2007 For SageTV 2.2-6.3

Jetty Log (tried on two browsers):

192.168.1.1 - - [14/Dec/2008:15:34:49 +0000] "GET /sage/m/menu.jsp HTTP/1.1" 503 1322 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4"
206.53.144.101 - - [14/Dec/2008:15:35:25 +0000] "GET /sage/m/menu.jsp HTTP/1.0" 503 1322 "-" "BlackBerry8330/4.5.0.89 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/105"

The only thing that seems relavent from the sage log is the fact that the jetty engine started:

Sun 12/14 10:12:12.384 Loading startup runnable:sagex.jetty.starter.Main
Sun 12/14 10:12:12.386 Loaded startup runnable:sagex.jetty.starter.Main

I noticed that my "C:\Program Files\SageTV\SageTV\jetty\webapps\SageWebApp" folder was empty (not sure if the war file should be extracting itself here?). I did extract the files to this folder, but still got the same error.

Any thoughts?

[jreichen]

Originally Posted by matt91

I noticed that my "C:\Program Files\SageTV\SageTV\jetty\webapps\SageWebApp" folder was empty (not sure if the war file should be extracting itself here?). I did extract the files to this folder, but still got the same error.

Check out post #26 above and see if that fixes your problem.

[jreichen]

Version 1.0.1 is now available. This is a set of bug fixes that have been posted in this thread since 1.0 was released.

1.0.1 December 14, 2008

• Fix exception casting java.lang.Integer to java.lang.Long when scheduling a manual recording that causes conflicts.
• Fix formatting of manual recording conflict page.
• Fix error message for invalid airing id on conflict resolution page.
• Change order of welcome file list to put menu.jsp first. (If the user enters a URL without a file name at the end, the server will look for menu.jsp first, followed by home.jsp, and finally index.jsp.) Now the menu page can be accessed using the URL http://<server>:<port>/sage/m

[jreichen]

Originally Posted by archie658

I'm not sure if the version I'm now using needs the xerces.jar, because I've tried several in the past. BTW, Xerces is a generic xml toolkit: http://xml.apache.org).

Can you try a couple of things?

1. Remove xerces.jar (back it up somewhere), restart Sage, and try xmltv and the mobile web interface
2. If that doesn't work, download the latest xerces.jar from Apache's web site, restart Sage, and try them again

[jreichen]

Originally Posted by archie658

Update: It's working on the second server. Looks really nice! And even better, it can be reverse proxied through SSL, so it can be made secure as well. The image dir must also be redirected, but it doesn't conflict with webserver 2.22.

Is it possible to set up the reverse proxy with http://<server>:<port>/sagem pointing to http://<server>:<port>/sage/m? That would eliminate the need to set up mapping for each item under /sage.

I haven't had a lot of luck setting up my reverse proxy, but I'm running Apache on a different server than Sage and I think that is a little different than using it on the same server. There's another thread that has a little bit of discussion around reverse proxy, but there are still some open items remaining (that's probably a better place to continue this discussion). If you or anybody else wants to document it, feel free to post there or even create a wiki page

I tried to eliminate any hard-coding of the /sage path in the mobile web server. Nielm's web server has it in a few places. It hasn't been updated in a while but it would be nice to know what all the issues are.

Originally Posted by archie658

Why did you choose to make a search function for the recordings in stead of for the future airings? Recordings are already listed. I didn't get that part.

I plan on adding other search pages. I'm going to put the different search types on their own page to keep the pages a little bit simpler given the size of mobile device screens.

I created the first one for recordings because that's what I use most I search for all recordings where the filename is *.mpg then add them to the conversion queue. Right now the filters on the listings page are enough for me to find the airings I need. I'll put airing search on my todo list.

Originally Posted by archie658

And since there's such a nice Conversions page, I was looking for 'streaming' link as well .

Conversions are easy. They're part of the SageTV core When I think of streaming, I think of what Placeshifter can do: automatically re-encode to a usable bitrate, and jump to any location in the file. The SageTV core doesn't expose that, and it's much harder for me to write myself.