Plugin: SageTV Web Interface V2 for Jetty

[wayner]

I renamed it servlet.jar.old so it should be getting picked up. I will try turning debug logging on and see what I get. Will it show which Jetty modules are being loaded?

Edit- What am I looking for in the logs - does this help?

Tue 10/13 20:06:45.956 [Jetty Starter@13757ec] (org.mortbay.log) <DEBUG> XML org.mortbay.jetty.webapp.WebAppContext@18c9b49{/,null}.setContextPath(/sage)
Tue 10/13 20:06:45.957 [Jetty Starter@13757ec] (org.mortbay.log) <DEBUG> XML org.mortbay.jetty.webapp.WebAppContext@18c9b49{/sage,null}.setWar(C:\Program Files\SageTV\SageTV\jetty/webapps/nielm_sagewebserver.war)
Tue 10/13 20:06:45.957 [Jetty Starter@13757ec] (org.mortbay.log) <DEBUG> XML org.mortbay.jetty.webapp.WebAppContext@18c9b49{/sage,C:\Program Files\SageTV\SageTV\jetty/webapps/nielm_sagewebserver.war}.setExtractWAR(true)
Tue 10/13 20:06:45.962 [Jetty Starter@13757ec] (org.mortbay.log) <DEBUG> XML org.mortbay.jetty.webapp.WebAppContext@18c9b49{/sage,C:\Program Files\SageTV\SageTV\jetty/webapps/nielm_sagewebserver.war}.setCopyWebDir(true)
Tue 10/13 20:06:45.967 [Jetty Starter@13757ec] (org.mortbay.log) <WARN> Config error at <Set name="mimeTypes">
      <New class="sagex.jetty.content.MimeTypes"><Set name="location">webserver/mime.types</Set></New>
   </Set>
Tue 10/13 20:06:45.967 [Jetty Starter@13757ec] (org.mortbay.log) <WARN> EXCEPTION 
Tue 10/13 20:06:45.967 [Jetty Starter@13757ec] java.lang.ClassNotFoundException: sagex.jetty.content.MimeTypes
Tue 10/13 20:06:45.967 [Jetty Starter@13757ec] 	at java.net.URLClassLoader$1.run(Unknown Source)
Tue 10/13 20:06:45.967 [Jetty Starter@13757ec] 	at java.security.AccessController.doPrivileged(Native Method)
Tue 10/13 20:06:45.967 [Jetty Starter@13757ec] 	at java.net.URLClassLoader.findClass(Unknown Source)
Tue 10/13 20:06:45.967 [Jetty Starter@13757ec] 	at java.lang.ClassLoader.loadClass(Unknown Source)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at java.lang.ClassLoader.loadClass(Unknown Source)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at org.mortbay.util.Loader.loadClass(Loader.java:91)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at org.mortbay.xml.XmlConfiguration.nodeClass(XmlConfiguration.java:216)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:564)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:907)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:829)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at org.mortbay.xml.XmlConfiguration.set(XmlConfiguration.java:278)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:240)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:206)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at org.mortbay.jetty.deployer.ContextDeployer.createContext(ContextDeployer.java:369)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at org.mortbay.jetty.deployer.ContextDeployer.deploy(ContextDeployer.java:263)
Tue 10/13 20:06:45.968 [Jetty Starter@13757ec] 	at org.mortbay.jetty.deployer.ContextDeployer.access$000(ContextDeployer.java:67)
Tue 10/13 20:06:45.969 [Jetty Starter@13757ec] 	at org.mortbay.jetty.deployer.ContextDeployer$ScannerListener.fileAdded(ContextDeployer.java:89)
Tue 10/13 20:06:45.969 [Jetty Starter@13757ec] 	at org.mortbay.util.Scanner.reportAddition(Scanner.java:417)
Tue 10/13 20:06:45.969 [Jetty Starter@13757ec] 	at org.mortbay.util.Scanner.reportDifferences(Scanner.java:331)
Tue 10/13 20:06:45.969 [Jetty Starter@13757ec] 	at org.mortbay.util.Scanner.scan(Scanner.java:286)
Tue 10/13 20:06:45.969 [Jetty Starter@13757ec] 	at org.mortbay.jetty.deployer.ContextDeployer.doStart(ContextDeployer.java:327)
Tue 10/13 20:06:45.969 [Jetty Starter@13757ec] 	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
Tue 10/13 20:06:45.969 [Jetty Starter@13757ec] 	at org.mortbay.jetty.Server.doStart(Server.java:199)
Tue 10/13 20:06:45.969 [Jetty Starter@13757ec] 	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
Tue 10/13 20:06:45.969 [Jetty Starter@13757ec] 	at sagex.jetty.starter.JettyInstance.doStart(Unknown Source)
Tue 10/13 20:06:45.969 [Jetty Starter@13757ec] 	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
Tue 10/13 20:06:45.969 [Jetty Starter@13757ec] 	at sagex.jetty.starter.Main.restartJetty(Unknown Source)
Tue 10/13 20:06:45.969 [Jetty Starter@13757ec] 	at sagex.jetty.starter.Main.run(Unknown Source)
Tue 10/13 20:06:45.970 [Jetty Starter@13757ec] 	at java.lang.Thread.run(Unknown Source)
Tue 10/13 20:06:45.970 [Jetty Starter@13757ec] (org.mortbay.log) <WARN> ContextDeployer$Scanner failed on 'C:\Program Files\SageTV\SageTV\jetty\contexts\nielm_websrv.context.xml

[jreichen]

You don't have the latest copy of jetty-starter.jar in your JARs folder. Did you upgrade the Jetty plugin to 1.6, and did that jar file get overwritten when you upgraded Jetty? If you open that jar file in WinZip you should see a sagex.jetty.content.MimeTypes file in there.

[wayner]

I will check that out - I haven't upgraded Jetty recently - I thought I was running 1.6. I think the last time I upgraded was around the time that Slugger released SJQ 2.0.

When upgrading what old files can I keep - can I keep all of the .properties files so that my config such as password, ports, etc. don't change?

[jreichen]

Yes, backup JettyStarter.properties and realm.properties if you have made any changes to them. Then reapply the changes after extracting the zip file.

[jreichen]

Originally Posted by matt91

I'm not sure if you guys have any place you'd like feature requests sent, so I'll just toss this one out here.

In some future release, would it be possible to list the year in the date field? I notice it the "past airings" for an old favorite. I know I can click through to see the details screen which reveals the year, but it'd be nice to have it on the listing here as well. There might be other no-year date listings elsewhere, but I just happened to notice this one.

thanks
Matt

(this airing is 3 years old...glad my wiz.bin is still going strong!)

I just uploaded 2.26 snapshot build 30 to SourceForge that includes this change. The files aren't visible yet but should show up shortly.

[Comitizer]

Hello All,

First off let me say that I love the new Jetty version of the web interface. I installed it a few days ago and everything seems to be working perfectly.

I set up a reverse proxy so that I can use the interface through my WHS site (which is working very well) but I'd like to edit the menu so that it has a link back to my WHS site.

Is this supported in the jetty version? I tried to edit the menu file but I couldn't save it (Windows gave me a sharing violation). I know I can probably get around it by stopping Sage but I'm concerned that my menu might get overwritten next time jetty deploys the war. Is there a better way to do this?

Thanks!

[matt91]

Originally Posted by jreichen

I just uploaded 2.26 snapshot build 30 to SourceForge that includes this change. The files aren't visible yet but should show up shortly.

great, thanks. i'll give it a go this weekend.

edit: Just installed jetty build 30, and it seems to work fine. Thanks for adding the year so quickly.

Matt

[Taddeusz]

Anyone know why this happens? I believe it's always been this way. Wondering if there was a way to hide this?

[Skirge01]

I've read through this thread about 6 times and I still can't figure out what I've done wrong, so here's what I did, step-by-step:

*** Instructions deleted because they were outdated ***
See this post for current instructions.

I'm pretty sure that's everything. I'm attaching the error log from Jetty. I do see some things that point to an issue, but I don't understand them.

EDIT: After examining the log file and looking at the other two files you provided (exe and zip) on the original post, do I need to download one of those, as well as the "new" one? I'm thinking that's where I got all screwed up. It sounded like I only needed the new one, but that's not the case, is it?

[wayner]

I upgraded Jetty to 1.6 (by unzipping the 1.6 file to my Sage directory slecting overwrite all), applied my changes to jettystarter.properties and realm.properties but now it appears that Jetty won't start at all as all of my Jetty apps are broken. Here is what looks like errors in the log file.

It appears as if there is an error for mimeTypes and addHandler, etc

Thu 10/15 22:29:11.976 [Jetty Starter@12c8b14] (org.mortbay.log) <DEBUG> XML org.mortbay.jetty.handler.ContextHandler@1d7a36e{/,null}.setResourceBase(C:\Program Files\SageTV\SageTV\jetty/static)
Thu 10/15 22:29:11.977 [Jetty Starter@12c8b14] (org.mortbay.log) <DEBUG> XML new class org.mortbay.jetty.handler.ResourceHandler
Thu 10/15 22:29:11.977 [Jetty Starter@12c8b14] (org.mortbay.log) <DEBUG> XML ResourceHandler@1095693.setMimeTypes(sagex.jetty.content.MimeTypes@2abefe)
Thu 10/15 22:29:11.978 [Jetty Starter@12c8b14] (org.mortbay.log) <WARN> Config error at <Set name="mimeTypes">
                        <Ref id="mimeTypes"/>
                      </Set>
Thu 10/15 22:29:11.978 [Jetty Starter@12c8b14] (org.mortbay.log) <WARN> Config error at <Call name="addHandler"><Arg>
                    <New class="org.mortbay.jetty.handler.ResourceHandler"><Set name="mimeTypes">
                        <Ref id="mimeTypes"/>
                      </Set></New>
                  </Arg></Call>
Thu 10/15 22:29:11.978 [Jetty Starter@12c8b14] (org.mortbay.log) <WARN> Config error at <Set name="handlers">
          <Array type="org.mortbay.jetty.Handler"><Item>
              <Ref id="RewriteHandler"><Set name="handler">
                  <New id="Contexts" class="org.mortbay.jetty.handler.ContextHandlerCollection"/>
                </Set></Ref>
            </Item><Item>
              <New class="org.mortbay.jetty.handler.ContextHandler"><Set name="mimeTypes">
                  <New id="mimeTypes" class="sagex.jetty.content.MimeTypes"/>
                </Set><Set name="contextPath">/</Set><Set name="resourceBase"><SystemProperty name="jetty.home" default="."/>/static</Set><Call name="addHandler"><Arg>
                    <New class="org.mortbay.jetty.handler.ResourceHandler"><Set name="mimeTypes">
                        <Ref id="mimeTypes"/>
                      </Set></New>
                  </Arg></Call></New>
            </Item><Item>
              <New id="DefaultHandler" class="org.mortbay.jetty.handler.DefaultHandler"><Set name="serveIcon">false</Set></New>
            </Item><Item>
              <New id="RequestLog" class="org.mortbay.jetty.handler.RequestLogHandler"/>
            </Item></Array>
        </Set>
Thu 10/15 22:29:11.978 [Jetty Starter@12c8b14] (org.mortbay.log) <WARN> Config error at <Set name="handler">
      <New id="Handlers" class="org.mortbay.jetty.handler.HandlerCollection"><Set name="handlers">
          <Array type="org.mortbay.jetty.Handler"><Item>
              <Ref id="RewriteHandler"><Set name="handler">
                  <New id="Contexts" class="org.mortbay.jetty.handler.ContextHandlerCollection"/>
                </Set></Ref>
            </Item><Item>
              <New class="org.mortbay.jetty.handler.ContextHandler"><Set name="mimeTypes">
                  <New id="mimeTypes" class="sagex.jetty.content.MimeTypes"/>
                </Set><Set name="contextPath">/</Set><Set name="resourceBase"><SystemProperty name="jetty.home" default="."/>/static</Set><Call name="addHandler"><Arg>
                    <New class="org.mortbay.jetty.handler.ResourceHandler"><Set name="mimeTypes">
                        <Ref id="mimeTypes"/>
                      </Set></New>
                  </Arg></Call></New>
            </Item><Item>
              <New id="DefaultHandler" class="org.mortbay.jetty.handler.DefaultHandler"><Set name="serveIcon">false</Set></New>
            </Item><Item>
              <New id="RequestLog" class="org.mortbay.jetty.handler.RequestLogHandler"/>
            </Item></Array>
        </Set></New>
    </Set>
Thu 10/15 22:29:11.979 [Jetty Starter@12c8b14] (org.mortbay.log) <INFO> class org.mortbay.jetty.handler.ResourceHandler.setMimeTypes(class sagex.jetty.content.MimeTypes)

[razrsharpe]

Originally Posted by wayner

I upgraded Jetty to 1.6 (by unzipping the 1.6 file to my Sage directory slecting overwrite all), applied my changes to jettystarter.properties and realm.properties but now it appears that Jetty won't start at all as all of my Jetty apps are broken. Here is what looks like errors in the log file.

It appears as if there is an error for mimeTypes and addHandler, etc

IIRC there are versioned (duplicate) jars that need to be removed from the \SageTV\JARS folder ... the install (upgrade) instructions in the wiki should tell you which ones to remove, etc

[matt91]

Originally Posted by jreichen

• Windows installer for web interface with TJWS
  
• Zip file for web interface with TJWS
  
• NEW: Zip file for web interface with Jetty

Is it possible to perhaps update the first post to clarify the file naming convention? I just downloaded and installed the snapshot build 30, but I initially grabbed the TJWS version because I wasn't sure which to get (I thought I wanted the one without "nielm" in the name - which was incorrect).

you can deduce the names by hovering over the list above, but it might be cleaner to have a naming convention clearly specified.

thanks
Matt

[Skirge01]

I was thinking the same thing. At this point, I'm pretty confident that's where I screwed up. So, you actually need either the 1st or 2nd one, plus the 3rd one?

[sleonard]

The first and second choices are Nielm's original webserver. One in zip format and one with an installer. Neither of these are for Jetty.

The 3rd one is the Jetty version of Nielm's webserver. This is the only one you should d/l if you want to run it in Jetty.

No matter what you should only d/l and install ONE of these three.

S

[Skirge01]

Darn. Then I'm back to not knowing what I messed up with my installation. Thanks for preventing me from doing further harm, at least!

[Skirge01]

I figured out my issue. I needed to remove this line from sage.properties:

nielm/webserver/root=webserver

Additionally, while I haven't verified every function, this line no longer seems to serve any purpose:

nielm/webserver/port=xxxx

Great work on this, jreichen! To recap, here are the exact steps I followed for switching to the Jetty version:

Please see the official Wiki Page from jreichen for the latest instructions. I'm placing the text which was below into an attachment just so that the original info isn't lost. I'll be happy to delete it once some people have verified the Wiki (no offense intended to jreichen). Just precautionary.

[jreichen]

Thanks for documenting your steps. These will eventually be on the wiki but I haven't had time to post them yet. Thanks to all you early adopters for helping to iron things out.

Steps 8 and 9 are not required for SSL to work. dataConstraint=2 always forces the connection over to the SSL port when you try to access the non-SSL port. Changing authentication to true for /public URLs would require 3rd party plugins and media players to authenticate when accessing RSS links and media for playback and some do not support that.

If you don't apply steps 8 and 9, you can still access your server using SSL by entering the URL https://<server>:<jetty_ssl_port>/sage/Home in your browser.

[Skirge01]

Originally Posted by jreichen

Thanks for documenting your steps. These will eventually be on the wiki but I haven't had time to post them yet. Thanks to all you early adopters for helping to iron things out.

Steps 8 and 9 are not required for SSL to work. dataConstraint=2 always forces the connection over to the SSL port when you try to access the non-SSL port. Changing authentication to true for /public URLs would require 3rd party plugins and media players to authenticate when accessing RSS links, XML links, and media for playback and some do not support that.

If you don't apply steps 8 and 9, you can still access your server using SSL by entering the URL https://<server>:<jetty_ssl_port>/sage/Home in your browser.

Just so that I'm clear and can update my post accurately, you're saying that the second location which has the dataConstraint=2 is only for 3rd party access. So, that doesn't need to be set and the authenticate part doesn't need to be set to true? But, both need to be set in the first location, correct?

If that's the case, then the first dataConstraint should be set to 2 only if you want to force SSL and the authenticate still needs to be set to true. Am I getting this straight yet?

[jreichen]

Originally Posted by Skirge01

Just so that I'm clear and can update my post accurately, you're saying that the second location which has the dataConstraint=2 is only for 3rd party access.

Yes. But in my post I said one of the things it applies to is XML links. I looked over the code again and that's incorrect.

Originally Posted by Skirge01

So, that doesn't need to be set and the authenticate part doesn't need to be set to true?

It really depends on whether a user accesses /public URLs with a client that can handle SSL ("dataConstraint") and/or authentication ("authenticate"). But as a general rule, that setting should retain the default values so clients that don't handle authentication can access those URLs.

Originally Posted by Skirge01

But, both need to be set in the first location, correct?

The settings are independent of each other. "Authenticate" should always be true (unless the user wants to completely disable authentication for this app), and "dataConstraint" can be set to "2" if the user wants to force everything over to the SSL port.

I guess that's what you're saying here:

Originally Posted by Skirge01

If that's the case, then the first dataConstraint should be set to 2 only if you want to force SSL and the authenticate still needs to be set to true. Am I getting this straight yet?

Hopefully that helps.

[Skirge01]

I believe I got it then. I edited the steps above, deleting the original step 9 and changing step 8, based on what you said. Hopefully I got it this time.