Plugin: SageTV Web Interface V2 for Jetty

[jreichen]

Originally Posted by matt91

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

Originally Posted by 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

I updated the first post in this thread as well as the version 2.25 announcement in post 2356 of the original thread. I'll continue to refine these based on questions and suggestions from users.

Thanks!

[wayner]

HELP

I followed all of the instructions above and I am still having problems. I did all of the steps above to install the Jetty Sage Web server. Initially all of Sluggers Jetty apps worked but the Jetty SageWeb and the mobile Jetty SageWeb apps did not work.

Then I realized that I had not yet applied my upgrade to Jetty 1.6. I did that upgrade from 1.5 and now none of my Jetty apps work! I get not found errors - not the Jetty errors but the basic internet errors.

jreichen - Any ideas on what to try next? It appears that Jetty is not running at all.

Here is some of my log that seems to deal with all of the Jetty stuff:

Sat 10/17 22:40:32.734 [Jetty Starter@1be1e0f] (org.mortbay.log) <INFO> Jetty Starter plugin version 1.6
Sat 10/17 22:40:32.734 [Jetty Starter@1be1e0f] (org.mortbay.log) <INFO> Starting Jetty
Sat 10/17 22:40:32.775 [HotplugStorage@116f944] StorageDeviceDetector started...
Sat 10/17 22:40:32.808 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> JettyStarter properties
Sat 10/17 22:40:32.808 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> java.io.PrintWriter@14704d9
Sat 10/17 22:40:32.808 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> Starting Jetty from the following configuration files: 'C:\Program Files\SageTV\SageTV\jetty/etc/jetty.xml'
Sat 10/17 22:40:32.812 [LibraryImporter@3c6543] Redetecting format for TV file because it changed:MediaFile[id=1846616 A[1547252,1547155,"The Backyardigans",17639@1012.00:00,30] host=standrews encodedBy= format=AVI 0:29:58 1769 kbps [#0 Video[MPEG4-Video 29.97 fps 720x480 4:3 progressive]#1 Audio[MP2 48000 Hz 2 channels 256 kbps idx=1]{MediaType=TV, OriginalAirDate=2004-10-11, MediaProviderDataID=tvdb:74808, MediaTitle=The Backyardigans, UserRating=9}] \\standrews\videos\Isabella's Shows\Backyardigans\SuperHeroesvsSuperVillains-1547252-0.avi, Seg0[Sun 10/12 0:00:01.195-Sun 10/12 0:30:09.095]]
Sat 10/17 22:40:32.813 [LibraryImporter@3c6543] Now using external format detector...
Sat 10/17 22:40:32.818 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> Checking Resource aliases
Sat 10/17 22:40:32.820 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> parse: file:/C:/Program%20Files/SageTV/SageTV/jetty/etc/jetty.xml
Sat 10/17 22:40:32.821 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> parsing: sid=file:/C:/Program%20Files/SageTV/SageTV/jetty/etc/jetty.xml,pid=null
Sat 10/17 22:40:32.840 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> resolveEntity(-//Mort Bay Consulting//DTD Configure//EN, http://jetty.mortbay.org/configure.dtd)
Sat 10/17 22:40:32.840 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> Redirected entity http://jetty.mortbay.org/configure.dtd --> jar:file:/C:/Program%20Files/SageTV/SageTV/JARs/jetty-6.1.11.jar!/org/mortbay/xml/configure_6_0.dtd
Sat 10/17 22:40:32.917 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML new class org.mortbay.thread.QueuedThreadPool
Sat 10/17 22:40:32.919 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML org.mortbay.thread.QueuedThreadPool@5f1c5e.setMinThreads(10)
Sat 10/17 22:40:32.920 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML org.mortbay.thread.QueuedThreadPool@5f1c5e.setMaxThreads(200)
Sat 10/17 22:40:32.920 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML org.mortbay.thread.QueuedThreadPool@5f1c5e.setLowThreads(20)
Sat 10/17 22:40:32.920 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML org.mortbay.thread.QueuedThreadPool@5f1c5e.setSpawnOrShrinkAt(2)
Sat 10/17 22:40:32.921 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML Server@141e734.setThreadPool(org.mortbay.thread.QueuedThreadPool@5f1c5e)
Sat 10/17 22:40:32.923 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> Container Server@141e734 + org.mortbay.thread.QueuedThreadPool@5f1c5e as threadpool
Sat 10/17 22:40:32.926 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML new class org.mortbay.jetty.nio.SelectChannelConnector
Sat 10/17 22:40:32.931 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML SelectChannelConnector@0.0.0.0:0.setHost(null)
Sat 10/17 22:40:32.933 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML SelectChannelConnector@0.0.0.0:0.setPort(8081)
Sat 10/17 22:40:32.934 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML SelectChannelConnector@0.0.0.0:8081.setMaxIdleTime(30000)
Sat 10/17 22:40:32.934 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML SelectChannelConnector@0.0.0.0:8081.setAcceptors(2)
Sat 10/17 22:40:32.934 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML SelectChannelConnector@0.0.0.0:8081.setStatsOn(false)
Sat 10/17 22:40:32.935 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> Statistics on = false for SelectChannelConnector@0.0.0.0:8081
Sat 10/17 22:40:32.935 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML SelectChannelConnector@0.0.0.0:8081.setConfidentialPort(8443)
Sat 10/17 22:40:32.935 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML SelectChannelConnector@0.0.0.0:8081.setLowResourcesConnections(5000)
Sat 10/17 22:40:32.935 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML SelectChannelConnector@0.0.0.0:8081.setLowResourcesMaxIdleTime(5000)
Sat 10/17 22:40:32.935 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML call addConnector
Sat 10/17 22:40:32.936 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> Container Server@141e734 + SelectChannelConnector@0.0.0.0:8081 as connector
Sat 10/17 22:40:32.937 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML new class org.mortbay.jetty.handler.rewrite.RewriteHandler
Sat 10/17 22:40:32.939 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML RewriteHandler@e95a72.setRewriteRequestURI(true)
Sat 10/17 22:40:32.939 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML RewriteHandler@e95a72.setRewritePathInfo(true)
Sat 10/17 22:40:32.940 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML RewriteHandler@e95a72.setOriginalPathAttribute(requestedPath)
Sat 10/17 22:40:32.943 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML new class org.mortbay.jetty.handler.rewrite.RewritePatternRule
Sat 10/17 22:40:32.943 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML org.mortbay.jetty.handler.rewrite.RewritePatternRule[ht][null][null].setPattern(/sagepublic/*)
Sat 10/17 22:40:32.943 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML org.mortbay.jetty.handler.rewrite.RewritePatternRule[ht][/sagepublic/*][null].setReplacement(/sage/public)
Sat 10/17 22:40:32.944 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML RewriteHandler@e95a72.setRules([Lorg.mortbay.jetty.handler.rewrite.Rule;@e6942e)
Sat 10/17 22:40:32.944 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML new class org.mortbay.jetty.handler.HandlerCollection
Sat 10/17 22:40:32.947 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML new class org.mortbay.jetty.handler.ContextHandlerCollection
Sat 10/17 22:40:32.950 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML RewriteHandler@e95a72.setHandler(ContextHandlerCollection@13e3b95)
Sat 10/17 22:40:32.950 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML new class org.mortbay.jetty.handler.ContextHandler
Sat 10/17 22:40:32.952 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML new class sagex.jetty.content.MimeTypes
Sat 10/17 22:40:32.965 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML org.mortbay.jetty.handler.ContextHandler@2eade0{/,null}.setMimeTypes(sagex.jetty.content.MimeTypes@99504b)
Sat 10/17 22:40:32.966 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML org.mortbay.jetty.handler.ContextHandler@2eade0{/,null}.setContextPath(/)
Sat 10/17 22:40:32.966 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML org.mortbay.jetty.handler.ContextHandler@2eade0{/,null}.setResourceBase(C:\Program Files\SageTV\SageTV\jetty/static)
Sat 10/17 22:40:32.968 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML new class org.mortbay.jetty.handler.ResourceHandler
Sat 10/17 22:40:32.969 [Jetty Starter@1be1e0f] (org.mortbay.log) <DEBUG> XML ResourceHandler@aad730.setMimeTypes(sagex.jetty.content.MimeTypes@99504b)
Sat 10/17 22:40:32.969 [Jetty Starter@1be1e0f] (org.mortbay.log) <WARN> Config error at <Set name="mimeTypes">
                        <Ref id="mimeTypes"/>
                      </Set>
Sat 10/17 22:40:32.969 [Jetty Starter@1be1e0f] (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>
Sat 10/17 22:40:32.970 [Jetty Starter@1be1e0f] (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>
Sat 10/17 22:40:32.970 [Jetty Starter@1be1e0f] (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>
Sat 10/17 22:40:32.970 [Jetty Starter@1be1e0f] (org.mortbay.log) <INFO> class org.mortbay.jetty.handler.ResourceHandler.setMimeTypes(class sagex.jetty.content.MimeTypes)

[jreichen]

Make sure to follow the upgrade instructions for removing Jetty 6.1.7 and 6.1.11 files. Version 1.6 of the plugin comes with Jetty 6.1.19 and the older files need to be removed. Restart Sage after cleaning out the older files.

The install page shows the structure of files installed by the plugin.

[wayner]

Awesome - that did the trick - deleting some old JARs

[wayner]

Spoke slightly too soon - the Sage Mobile Web server isn't working. It says "HTTP ERROR 404
Problem accessing /sage/m/menu.jsp. Reason:

NOT_FOUND"

That's your app as well, isn't it. Any reason why I can't just reinstall the Sage Mobile on top of the existing structure?

One more thing - I use the Vista Sage Gadget that shows what is currently recording. Is this compatible with the Jetty server?

[jreichen]

Originally Posted by wayner

HTTP ERROR 404
Problem accessing /sage/m/menu.jsp. Reason: NOT_FOUND

That was the original path for the mobile web interface. But when Jetty support was added to nielm's, the mobile URL had to be changed to /sagem/m/menu.jsp. Is it documented wrong somewhere?

Originally Posted by wayner

That's your app as well, isn't it. Any reason why I can't just reinstall the Sage Mobile on top of the existing structure?

Yes it is. It can be reinstalled like that but I think your problem is you're using the old URL.

Originally Posted by wayner

One more thing - I use the Vista Sage Gadget that shows what is currently recording. Is this compatible with the Jetty server?

It should still work. If you're running SageTV version 5 you might need a fix from me. If you're running SageTV version 6 it should work.

[wayner]

Thanks - I downloaded and re-installed the latest Mobile Web server and it is now working - FYI I am running Sage 6.6.2.218 - I am surprised that people still run version 5! That doesn't help you if you have HD-PVRs.

The only thing outstanding is the Vista Gadget (which I also have running on my Win7 RC machine). It says can't connect in the default Now Recording window but when I click on it to see upcoming recordings it gives me a list so it seems to be "kind of" working. Note that I went to the sage.js file and changed the URL to "/sage/Home" rather than "/sage/home" and I did update the port in my Options.

D'oh - it looks like you have to capitalize "home" in a couple of lines:
var HOME_URL = "/sage/Home";
var CURRENT_URL = "/sage/Home?xml=currrecording";

[Taddeusz]

Does nobody seem to care about the streaming in the web server? I realize that most of the time I can go to Hulu or wherever and watch the same shows. But those streams are heavier on the bandwidth than the ones from my web server and from work that is a very important consideration.

The good news is since I upgraded my server from an AMD X2 4200 to a C2D E6550 streaming is a LOT more stable. I don't have the problems of the streaming side all of a sudden stops responding.

This may be a buffering issue with WMP but the main problem that I have right now is that if I pause playback for too long it appears that WMP drops the connection when the buffer is full and then VLC quits. Not sure if there is an option in WMP to fix this. Apparently WMP can only buffer up to 60 seconds of video. VLC can't connect through our proxy. Many times I need to step away from my desk for more than 60 seconds.

Any ideas?

[wayner]

What's the advantage of streaming in the web server vs. Placeshifter? I see the advantage for platforms that don't have Placeshifters, such as iPhones, Blackberries, etc., but if it is to a computer why not use PS?

[Taddeusz]

Originally Posted by wayner

What's the advantage of streaming in the web server vs. Placeshifter? I see the advantage for platforms that don't have Placeshifters, such as iPhones, Blackberries, etc., but if it is to a computer why not use PS?

Placeshifter will also not connect through our proxy.

[wayner]

Originally Posted by Taddeusz

Placeshifter will also not connect through our proxy.

Is this because certain ports are blocked?

[Taddeusz]

Originally Posted by wayner

Is this because certain ports are blocked?

Yes, they basically have everything locked down. I can connect to my router and web server on ports 8080 and 8081 but that's about it.

[kricker]

Originally Posted by Skirge01

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

1. Download nielm_websrv_jetty_2_25.zip
2. Shut down SageTV service (if applicable) and all clients
3. In your SageTV directory, delete the entire /webserver folder
4. In your SageTV directory, delete the following from the /JARs folder:

• servlet.jar
• nielm_sagewebserver.jar
• nielm_sageutls.jar
• nielm_sagexmlinfo.jar

5. In Sage.properties, find the load_at_startup_runnable_classes= entry and delete the net.sf.sageplugins.webserver.StartServer argument
6. In Sage.properties, delete the nielm/webserver/root=webserver entry
7. Extract the .zip file from step #1 to your SageTV folder, maintaining folder structure

If not forcing SSL, skip to step #9.

If you already have Jetty working with SSL and wish to force it's use for the web interface:
8. Uncomment the first instance of <Set name="dataConstraint">2</Set> (line 54) in the nielm_websrv.context.xml file

9. Restart the SageTV service

If anyone wants to copy these instructions and use them as their baseline, feel free to do so.

This helped me switch to the Jetty version pretty quickly, thank you. The only thing I got hung up on is the fact that you need to get jetty installed and running first. This may seem like a no brainier, but I wasn't sure if the .zip on the first post included everything I needed or not. Seeing as how the above post said "the exact steps" to switch I thought maybe that was the case. I quickly figured out that indeed I need to go get the newest jetty starter first and follow it's install directions first. I also did not delete the "nielm_sageutls.jar" file as I know that is used by other add-ins.

[Skirge01]

Thanks for the feedback. I went ahead and updated my post with a note about needing Jetty installed first, as well as that the *utls.jar may be required by other plug-ins.

[Skirge01]

I can't seem to get the Mobile page to come up. I read in an earlier post in this thread that the new address is https://[servername]:[port]/sagem/m/menu.jsp, but that gives me a 404 error:

HTTP ERROR: 404

Problem accessing /sagem/m/menu.jsp. Reason:

NOT_FOUND

I've tried redownloading the nielm_websrv_jetty_2_x.zip file and unzipping it a second time while both service and client are down, but I keep getting the same error.

Let me know if you need any log files.

[Slugger]

The zip file you downloaded is not the mobile web server, but just the nielm server ported to Jetty. To access the server you've downloaded and installed, visit: /sage/Home

[Skirge01]

Guess I misunderstood another couple of posts I read. The normal web interface is working perfectly. I was under the impression that the mobile interface was also currently supported in your Jetty conversion. Is it not supported (yet?) or do I need to tweak things between a couple of downloads to try and get it working?

EDIT: Yep, I'm an idiot. :-) I was getting this and the mobile interface confused, thinking they were integrated. My bad. Sorry about that. They should both work, once they're installed, though, right?

[razrsharpe]

Originally Posted by Skirge01

EDIT: Yep, I'm an idiot. :-) I was getting this and the mobile interface confused, thinking they were integrated. My bad. Sorry about that. They should both work, once they're installed, though, right?

yes...they both (normal and mobile app...separate app) work when installed under jetty

[Skirge01]

Thanks, razrsharpe. I'll have to figure out what I did to break it then because it worked prior to moving the regular web interface to Jetty. I went to unzip the mobile web zip file and the files already existed. If I figure out what I did to break it, I'll be sure to post it here.

[infocus13]

Hi guys

Recently installed the webserver for jetty on sagetv 6.6.2. Everything was working fine until today, when i started to get all sort of weird java errors when trying to access any of the search/file listing options in the webserver (i.e. sagetv > sage recording, medial library > search imported videos, etc).

The weird thing is that I havent changed anything in my setup and that I still get the webserver home page, its just that most of the options seems to be broken now. I've also tried to copy the jetty webserver files over to the sagetv directory, which didnt help.

Any help/suggestions appreciated. thanks.

Exception while processing servlet:
java.lang.NoClassDefFoundError: net/sf/sageplugins/webserver/AiringList
java.lang.NoClassDefFoundError: net/sf/sageplugins/webserver/AiringList
at net.sf.sageplugins.webserver.RecordingsServlet.doServletGet(RecordingsServlet.java:145)
at net.sf.sageplugins.webserver.SageServlet.doGet(SageServlet.java:86)
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:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
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:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
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:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)