Plugin: Jetty Starter 1.6

[jreichen]

You're welcome The only way I know of is to add the GzipFilter as a filter to the web application's web.xml file. You can look at the mobile web interface's web.xml file to see how I did it there.

Unfortunately stuckless doesn't deliver a web.xml, just a context xml file and I don't think it can be set in there.

If you're familiar with web applications you could use the mobile web interface as an example and create a war file for the remote apis that would only need a web.xml file (all the class files are in the sagex.jar file in the JARs folder so those don't need to be included in the war file). The context xml file would also need to be modified to deploy the war file (again, look at the mobile web interface for an example). Or maybe stuckless could do this for you but from what I understand he's very busy with the Phoenix project.

There might be a way to set it up at the server level but I haven't found a way to do it. It might require some more custom programming in the plugin. Even if it is possible, it might be better to leave it up to each app's developer to decide whether to support compression.

If you do manage to get the filter set up, remember that the HTTP request header 'Accept-Encoding' must include 'gzip'.

[kfontenot]

Can someone please help me get this plugin working. I'm trying to install it so that I can use Sage Job Queue. How can I test that I have installed it correctly? When I try to access SJQ though IE8 I cannot get a connection. Should I use a different browser? I'm running Vista 64 bit and Sage 6.5.16

[jreichen]

I don't run IE8 so I can't test this myself. Here are some things to try:

1. Does the sagetv_0.txt log have any clues? On Windows, I think you have to set debug_logging=TRUE in Sage.properties before it will write to that file.
2. Check the jetty/logs folder in the SageTV directory for any info in there.
3. Do you have an extension like ieHTTPHeaders installed? That will print out the HTTP requests and responses between client and server. That might help track down the problem.
4. Does IE8 muck with firewall or proxy settings?

The Jetty wiki has a page with some debugging and logging info that might be helpful for #1 and #2.

[Slugger]

Also be sure you didn't download the ssl version of SJQ. Or if you did, then make sure you've installed SSL support into Jetty properly. If you didn't setup SSL in Jetty then you can't use the ssl package of SJQ. You can tell if you've installed the SSL version by checking the browser's address bar - if it's always forwarding you to https://... even when trying to connect to http://... then you've installed the ssl version of SJQ.

[kfontenot]

I first tried instaling the non ssl version of SJQ. I then installed the ssl version. I also downloaded Firefox to see if a different browser would work. Once I generated a certificate it worked. Thanks for you suggestions and help.

[kfontenot]

Can someone tell me how I can create a trusted SSL certificate for Jetty.

[babgvant]

trusted by FF or IE? you'd need to get one from a CA... or you can import the one you have and call it "trusted".

[rmac321]

The wiki link is bad.

404 Not Found (No handler matched request to /wiki/Jetty)

Is this temporary?

[jreichen]

It looks like it's working again.

[QueOnda]

Installed jetty and working (using http://localhost:8080/bmt) (per instructions) but before I installed I had nielm's web server working. After jetty install nielm's web server not working. I get

HTTP ERROR: 404

NOT_FOUND

RequestURI=/sage/Home

Powered by jetty://

using http://127.0.0.1:8080/sage/Home

Thanks.

[amg]

Originally Posted by QueOnda

Installed jetty and working (using http://localhost:8080/bmt)
using http://127.0.0.1:8080/sage/Home

Thanks.

Can't have them both on the same port (8080) in your case. Move one of them to a different port, and then both will work.

[QueOnda]

Originally Posted by amg

Can't have them both on the same port (8080) in your case. Move one of them to a different port, and then both will work.

Thanks!!! That was it.

[DOS64K]

I'm trying out BMT for the first time, but can't seem to connect to jetty. I'm getting the following

HTTP ERROR: 404
NOT_FOUND
RequestURI=/bmt

Powered by jetty://

I'm using WHS and IE8, but I've also tired connecting from IE7 and I already use Neilms Webserver. And yes, I've changed the port to a different one than Neilms. It seems that the string for loading it in Sage.properties isn't working. Any ideas?

[jreichen]

Have you checked the jetty/contexts/bmt.xml file? There is a known issue with it. See Sean's post for more.

[DOS64K]

Originally Posted by jreichen

Have you checked the jetty/contexts/bmt.xml file? There is a known issue with it. See Sean's post for more.

I don't seem to have the bmt.xml file in question in the directory the post describes:

I think that there is a bug in my jetty context file (jetty/contexts/bmt.xml). Edit the file and look for these lines and make sure both are set to true.

I have the latest jetty version and have checked for that file in the zip file, but it wasn't there. Is it generated somehow or is it supposed to be in the download?

EDIT: Fixed. I had an earlier version of BMT from another link in a post. Should have figured that was the problem from the get-go. Thanks for the help just the same.

[jreichen]

The Jetty Starter plugin version 1.6 has been released and can be downloaded here. This mainly has changes that can be adopted in future releases of web applications.

• Upgrade Jetty from 6.1.11 to 6.1.19 - please be sure to follow the upgrade instructions in order to remove the 6.1.11 files or you will have problems.
• Support user-specified mime types. Plugin developers: you need to modify your app before users can customize mime types.
• Deliver jetty-ajp.xml and jetty-ajp.jar for Apache integration (unsupported). These were packaged with 6.1.19 so I included them for those of you who are interested in running Jetty behind Apache. I haven't worked with AJP so I will not be supporting it. If you use it feel free to post your instructions to the wiki.

Jason

[darcilicious]

For my setup, I have a Vista HTPC with SageTV installed as a service and do all my recordings. I also watch recordings and occasionally watch live tv or video files (from the media center) on what must be the "local client" (if I have that right).

I also have the SageTV client software installed on my Vista laptop for remote viewing over the network (my "remote client").

I have got Jetty 1.6 installed and working for the mobile web app and for the sagetweet plugin on the HTPC. However, I have noticed that neither of these plugins seem to be aware of the "local client" activities on the HTPC and certainly not aware of the "remote client".

I have been told by that I need to install Jetty on both my local and remote clients and then add the plugins to those Jetty installations.

However, I'm a little confused on how to do a separate installation on the "local client" since there can only be one jetty directory (I think) and one JettyStarter.properties in the SageTV directory. And even more confused on how to do one on the remote client where there isn't even a SageClient.properties file.

Is it even possible to have separate Jetty installs? If so, would you be able to point me the right direction? Thanks!

[jreichen]

It's been probably 3 years since I ran client and server on the same machine and I forgot about that setup when I created the Jetty plugin.

If I remember correctly, the client and server are installed in the same directory on Windows. If so, then right now it's not possible to run Jetty under both client and server from the same directory. I could change it to call a Sage API to check to see if Jetty is running in a client. If it is then I could do one of two things:

1. Look for a JettyStarterClient.properties file rather than JettyStarter.properties and start it from there.
2. Or, look for some client-specific properties in JettyStarter.properties.

The first one would be easier to implement.

I don't think you'll need to worry about client and server both using the same SAGE_HOME/jetty folder. You can test that for me when I have it fixed

You shouldn't have a problem running Jetty on your laptop. Just follow all the installation instructions on the wiki, except modify the load_at_startup_runnable_classes line in SageClient.properties not Sage.properties.

[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.

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.

Download it from here.

[frontlinegeek]

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.