Plugin: Jetty Starter 1.6

[toricred]

I don't think BMT includes JETTY.

[frontlinegeek]

Sorry, I meant the BMT.xml

I am using the latest JETTY...

Also, I have Sage set as a service if that matters at all (Which is how I had it before and it was fine.)

[jreichen]

Originally Posted by que3jxp

I am having a seemingly random issue...

I had JETTY installed once but I recently reinstalled my WHS box and now when installing JETTY, when I try to go to the web address for it, I get "invalid request".

Any ideas?

SageTV version is 6.6.1 and I am using the JETTY that comes in the current BMT package.

Please turn on Sage logging and check the log file for any error messages. If there isn't much there, uncomment the DEBUG= line from JettyStarter.properties, restart Sage, and see if anything else is printed. Also check the most recent file in the jetty/logs directory to see what requests are being made to Jetty from the client.

If you post those files here I can review them as well.

[darcilicious]

Originally Posted by jreichen

darcilicious, I created a build of the Jetty plugin to allow it to run under both the client and server on the same machine. Would you mind testing it out? I don't have a client installation.

Awesome, I've had a busy week and am just now able to play around with all this. I'll let you know how it goes Thanks so much!

[frontlinegeek]

Here is the glitch:

Sun 8/23 14:17:26.351 [SageTV@1766806] Loading startup runnable:sagex.jetty.starter.main
Sun 8/23 14:17:26.352 [SageTV@1766806] ERROR Loading startup runnable extension of:java.lang.ClassNotFoundException: sagex.jetty.starter.main

[frontlinegeek]

OK...

When I just posted that, I noticed for the first time that you have Main and not main in your instructions...

Changed that and now it works...

[darcilicious]

Originally Posted by jreichen

Follow the normal installation steps to get it running in the server. To run it in the client, modify the load_at_startup_runnable classes in SageClient.properties, then make a copy of JettyStarter.properties, name it JettyStarterClient.properties, and change the port in that file to something other than the existing port and nielm's web server's port.

I don't think it's working yet. Here's what I did:
-Stopped SageTV (clients and service)
-Installed the new Jetty files over the existing ones after I saved the JettyStarter.properties and jetty/etc/realm.properties files and then restored them
-Edited SageClient.properties by adding sagex.jetty.starter.Main to load_at_startup_runnable_classes
-Copied JettyStarter.properties to JettyStarterClient.properties and made the port number one higher than before (it's an available port)
-Started SageTV service
-Started local client
-Went to localhost:newportnumber and got "Page not found - connection failure"
-Went to localhostriginalportnumber and got the list of available contexts / webapps (sagetweet, sagem, and org.mortbay.jetty.handler.ContextHandler...

What can I try next for you?

(and thanks again for working on this! -- also if email is best, PM and I'll send you my email address...)

[darcilicious]

I will say that the jetty server is up and running fine now on my remote client (no problems, as you predicted ); it's the local client where I'm having problems. Cheers!

[Skirge01]

Wanted to say that I was able to upgrade successfully within a matter of 10 minutes. Absolutely no issues at all following the directions. I just needed to determine which version I was already running, so I knew which steps to follow. I wish all upgrades were this easy! Excellent job and thanks for the work on this!

[jreichen]

Originally Posted by darcilicious

I don't think it's working yet. Here's what I did:
-Stopped SageTV (clients and service)
-Installed the new Jetty files over the existing ones after I saved the JettyStarter.properties and jetty/etc/realm.properties files and then restored them
-Edited SageClient.properties by adding sagex.jetty.starter.Main to load_at_startup_runnable_classes
-Copied JettyStarter.properties to JettyStarterClient.properties and made the port number one higher than before (it's an available port)
-Started SageTV service
-Started local client
-Went to localhost:newportnumber and got "Page not found - connection failure"
-Went to localhostriginalportnumber and got the list of available contexts / webapps (sagetweet, sagem, and org.mortbay.jetty.handler.ContextHandler...

What can I try next for you?

(and thanks again for working on this! -- also if email is best, PM and I'll send you my email address...)

Both the client and server Jetty might be trying to monitor the same context files (under jetty/contexts).

Does the Jetty installed for SageTV server work if SageTV server is running but client is not? How about the same case for the SageTV client without the server running (I'm not even sure client will start up if it doesn't find the server)?

Can you turn on SageTV logging and post the SageTV client and server logs as well as the latest Jetty request log from the jetty/logs folder?

[evilpenguin]

I'm having trouble getting CGI working via Jetty, I looked at the doc and it didn't make much sense to me.

http://jetty.mortbay.org/jetty5/faq/...ent_t_CGI.html

The best I can figure is that I add this to my jetty.xml

  <Call name="addContext">
    <Arg>/cgi-bin/*</Arg>
    <Set name="ResourceBase">cgi-bin</Set>
    <Set name="ServingDynamicServlets">TRUE</Set>
    <Call name="addServlet">
      <Arg>Common Gateway Interface</Arg>
      <Arg>/</Arg>
      <Arg>com.mortbay.Servlet.CGI</Arg>
    </Call>
  </Call>

And drop the files into /jetty/cgi-bin/, but that doesn't seem to be working. Thoughts?

[loomdog32]

I am having issues getting Jetty setup..

I am copying the files to the Sage directory, adding

sagex.jetty.starter.Main

to Sage.Properties
and changing the port to 8070 in JettyStarter.Properties
No Joy

Turned in Sage Logging and this is what I get AFTER Jetty Loads

Thu 9/24 0:45:35.626 [Jetty Starter@1b0b0a0] 2009-09-24 00:45:35.929::WARN:  Config error at <Set name="mimeTypes">
                        <Ref id="mimeTypes"/>
                      </Set>
Thu 9/24 0:45:35.627 [Jetty Starter@1b0b0a0] 2009-09-24 00:45:35.929::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 9/24 0:45:35.627 [Jetty Starter@1b0b0a0] 2009-09-24 00:45:35.929::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 9/24 0:45:35.628 [Jetty Starter@1b0b0a0] 2009-09-24 00:45:35.929::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 9/24 0:45:35.628 [Jetty Starter@1b0b0a0] 2009-09-24 00:45:35.929::INFO:  class org.mortbay.jetty.handler.ResourceHandler.setMimeTypes(class sagex.jetty.content.MimeTypes)

[jreichen]

If you're upgrading the plugin, did you remove the jar files for Jetty 6.1.7 and 6.1.11? There are instructions on the wiki on how to do that.

The mime type API's weren't available in those versions (the plugin now comes with 6.1.19) so I suspect you have old jar files in your classpath.

[jreichen]

Darcilicious, were you able to get Jetty running in both the SageTV client and server on the same machine?

[jreichen]

Originally Posted by evilpenguin

I'm having trouble getting CGI working via Jetty, I looked at the doc and it didn't make much sense to me.

http://jetty.mortbay.org/jetty5/faq/...ent_t_CGI.html

The best I can figure is that I add this to my jetty.xml

  <Call name="addContext">
    <Arg>/cgi-bin/*</Arg>
    <Set name="ResourceBase">cgi-bin</Set>
    <Set name="ServingDynamicServlets">TRUE</Set>
    <Call name="addServlet">
      <Arg>Common Gateway Interface</Arg>
      <Arg>/</Arg>
      <Arg>com.mortbay.Servlet.CGI</Arg>
    </Call>
  </Call>

And drop the files into /jetty/cgi-bin/, but that doesn't seem to be working. Thoughts?

Based on my configuration of the "static" resource base in jetty.xml, you might try putting a "/" before cgi-bin.

<Set name="ResourceBase">/cgi-bin</Set>

Also, based on the source for the cgi servlet, it looks like it prints configuration info to the debug log. Turn on SageTV's debug logging and enable the DEBUG line in JettyStarter.properties and see if its output prints anything helpful.

[razrsharpe]

first thanks for putting this together... its fantastic to finally be running a single webserver...

feature request... or maybe you can already do this but i dont know how

when i navigate to http :// ipaddress : port/ i get a jetty 403 forbidden error... it would be fantastic if a list of links to all the installed applications (nielms Sage, Sagem, bmt, sagealert, sjq, etc, etc) was displayed instead... either at http :// ipaddress : port/ or ../Home

[rosemary]

Figured it might be helpful to crosspost some Jetty-related information I discovered while trying to work out a problem with BMT. Basically, on Windows the temporary files/directories created by Jetty don't always get cleaned up properly. In the case of BMT, this caused it to work fine the first time, but be screwed up on a Sage restart.

Anyone using a temporary directory in their jetty app should probably think about getting rid of it.

Here's a link to the bug report:
http://jira.codehaus.org/browse/JETTY-848

But it's a bug in the JVM itself (reported six years ago) and it looks like they're not too interested in fixing it:
http://bugs.sun.com/view_bug.do?bug_id=4950148

[GollyJer]

Originally Posted by razrsharpe

first thanks for putting this together... its fantastic to finally be running a single webserver...

feature request... or maybe you can already do this but i dont know how

when i navigate to http :// ipaddress : port/ i get a jetty 403 forbidden error... it would be fantastic if a list of links to all the installed applications (nielms Sage, Sagem, bmt, sagealert, sjq, etc, etc) was displayed instead... either at http :// ipaddress : port/ or ../Home

+1 This is a great idea.

[robogeek]

Originally Posted by razrsharpe

first thanks for putting this together... its fantastic to finally be running a single webserver...

feature request... or maybe you can already do this but i dont know how

when i navigate to http :// ipaddress : port/ i get a jetty 403 forbidden error... it would be fantastic if a list of links to all the installed applications (nielms Sage, Sagem, bmt, sagealert, sjq, etc, etc) was displayed instead... either at http :// ipaddress : port/ or ../Home

You can accomplish this manually by creating an index.html file in the SageTV\jetty\static directory. Just add the necessary html code with links to the jetty addons you have installed. Be sure you have a good username/password setup in the jetty\etc\realm.properties file. And be sure the default sage:frey username\password is deleted or commented out of that file...it would be a shame to wake up one morning to find that some Russian hacker removed all of your favorites and deleted all of your recordings. If any addons don't require authentication, you may not want to include them in the index.html since it could allow unwanted visitors playing with things they shouldn't be playing with. You could prevent this by placing the index.html with links to your jetty addons in the jetty\webapps\SageWebApp\webapp directory (assuming you have the SageTV Jetty Mobile Web App installed) and creating an index.html in the jetty\static directory that would be a welcome page with link to the password protected index.html in the Mobile Web App root directory.

A better approach would be for someone to write a script or program that can parse the xml files in the contexts directory and check them regularly for any updates. The script or program could then create and update a html file in the jetty\webapps\SageWebApp\webapp directory (assuming the Mobile Web App is installed) which is password protected by default. The script or program should be able to create or update the index.html with the appropriate links based on the info it parses out of the context xml files, and a .properties file could be used to override link names or to add additional links that you think would be useful that aren't going to be found in the context xml files. Then an index.html welcome page with a link to the new index.html in the SageWebApp\webapp directory could be created in the jetty\static directory. Or maybe a new Jetty addon could be created to accomplish the same thing, I don't know. Just thinking out loud here.

[razrsharpe]

Originally Posted by robogeek

You can accomplish this manually by creating an index.html file in the SageTV\jetty\static directory. Just add the necessary html code with links to the jetty addons you have installed.

sounds easy enough... but I'm an html neophyte... i may have a go at it though and see how far i get

Be sure you have a good username/password setup in the jetty\etc\realm.properties file. And be sure the default sage:frey username\password is deleted or commented out of that file...it would be a shame to wake up one morning to find that some Russian hacker removed all of your favorites and deleted all of your recordings. If any addons don't require authentication, you may not want to include them in the index.html since it could allow unwanted visitors playing with things they shouldn't be playing with. You could prevent this by placing the index.html with links to your jetty addons in the jetty\webapps\SageWebApp\webapp directory (assuming you have the SageTV Jetty Mobile Web App installed) and creating an index.html in the jetty\static directory that would be a welcome page with link to the password protected index.html in the Mobile Web App root directory.

good point

Or maybe a new Jetty addon could be created to accomplish the same thing, I don't know. Just thinking out loud here.

ya i think that would be the best approach ... then some setup/refreshing/etc could be included (and maybe general jetty configuration?)... I would attempt my hand at it... (i actually did look into it a bit about a week ago and got super lost )... but i can barely call myself a programmer.. and am definitely not familiar with html / jetty...