Plugin: Jetty Starter 1.6

[bthurber]

Originally Posted by perfessor101

Hello, I had Jetty working about a year ago ... then it seemed to stop responding ...
Bobby

Is it possible you have some old .jar files hanging around in SageTV/JARs directory?

[perfessor101]

Do you mean in the SageTV directory itself ?

Is there a central place listing which JAR files are the most current so I can compare it to the ones listed in my post?

or is the next step deleting my JAR directory and repopulating it from the Jetty 1.6, BMT 4.0 beta, TV Explorer and latest sagex files?

and are there any JAR files placed in the JAR directory by SageTV itself I shouldn't delete?

thanks for your help,
Bobby

[razrsharpe]

@ perfessor - you do have duplicate jars in your jars directory (and lots of them relate to jetty).

Sage does put jars in that directory that it depends on so just don't go deleting everything and starting over

from the log file you posted above (duplicates that I see are bold... i would probably delete either the older one or the one with the lower version number... after making a backup of course )

Sun 3/21 10:53:36.782 [main@df8f5e] classpath=
C:\Program Files\SageTV\SageTV\Sage.jar
C:\Program Files\SageTV\SageTV\xerces.jar
C:\Program Files\SageTV\SageTV\plugin.jar
C:\Program Files\SageTV\SageTV\
.
C:\Program Files\Java\jre6\lib\ext\QTJava.zip
JARs\activation.jar
JARs\ant-1.6.5.jar
JARs\commons-codec-1.3.jar
JARs\commons-codec.jar
JARs\commons-dbutils-1.3.jar
JARs\commons-dbutils.jar
JARs\commons-io-1.4.jar
JARs\commons-io.jar
JARs\commons-jxpath-1.1.jar
JARs\commons-lang-2.4.jar
JARs\commons-lang.jar
JARs\commons-logging-api.jar
JARs\commons-logging.jar
JARs\commons-vfs-20070823.jar
JARs\core-3.1.1.jar
JARs\df_sageutils.jar
JARs\gkusnick.sagetv.jar
JARs\h2.jar
JARs\htmlparser.jar
JARs\imageutils.jar
JARs\jcifs-1.1.6.jar
JARs\jdic.jar
JARs\jetty-6.1.11.jar
JARs\jetty-6.1.19.jar
JARs\jetty-ajp-6.1.19.jar
JARs\jetty-rewrite-handler-6.1.19.jar
JARs\jetty-sslengine-6.1.11.jar
JARs\jetty-sslengine-6.1.19.jar
JARs\jetty-starter.jar
JARs\jetty-util-6.1.11.jar
JARs\jetty-util-6.1.19.jar
JARs\jsp-2.1-jetty-6.1.19.jar
JARs\jsp-2.1.jar
JARs\jsp-api-2.1.jar
JARs\log4j-1.2.15.jar
JARs\log4j.jar
JARs\lucene-core-2.3.2.jar
JARs\lucene-core.jar
JARs\mail.jar
JARs\mailcheck.jar
JARs\metadata-updater.jar
JARs\mx4j-impl.jar
JARs\mx4j-jmx.jar
JARs\mx4j-remote.jar
JARs\mx4j-tools.jar
JARs\nielm_getrssnews.jar
JARs\nielm_sageimdb.jar
JARs\nielm_sagemenureader.jar
JARs\nielm_sageutls.jar
JARs\nielm_sagewebserver.jar
JARs\nielm_sagexmlinfo.jar
JARs\phoenix.jar
JARs\sagemc.jar
JARs\sageortus.jar
JARs\sagex.api.jar
JARs\sbbi-jmx-1.0.jar
JARs\sbbi-upnplib-1.0.3.jar
JARs\servlet-api-2.5-6.1.11.jar
JARs\servlet-api-2.5-6.1.19.jar
JARs\servlet.jar

[perfessor101]

Thanks razrsharpe that helped ...

I did a search on my installation drive for all the files that were in bold and kept the newest one from each couplet ...

The web pages are up although I haven't done any testing of the features I'm most curious about ...

here's the list of what I kept ...

 Directory of C:\Program Files\SageTV\SageTV\JARs
12/09/2007  09:45 PM            54,829 activation.jar
26/07/2009  01:50 PM         1,034,049 ant-1.6.5.jar
18/03/2010  05:22 PM            46,725 commons-codec.jar
18/03/2010  05:22 PM            41,376 commons-dbutils.jar
18/03/2010  05:22 PM           109,043 commons-io.jar
29/03/2006  10:26 AM           268,794 commons-jxpath-1.1.jar
18/03/2010  05:22 PM           261,809 commons-lang.jar
29/03/2006  10:26 AM            22,327 commons-logging-api.jar
29/03/2006  10:26 AM            31,605 commons-logging.jar
08/09/2009  10:02 PM           373,438 commons-vfs-20070823.jar
26/07/2009  01:50 PM         3,566,844 core-3.1.1.jar
13/10/2008  10:46 PM            18,293 df_sageutils.jar
13/01/2010  11:59 PM           582,133 gkusnick.sagetv.jar
18/03/2010  05:22 PM         1,241,864 h2.jar
18/03/2010  05:22 PM           288,098 htmlparser.jar
26/11/2008  11:48 AM             3,527 imageutils.jar
02/01/2009  06:12 PM           263,903 jcifs-1.1.6.jar
23/03/2005  10:45 AM            72,906 jdic.jar
26/07/2009  01:50 PM           526,754 jetty-6.1.19.jar
26/07/2009  01:50 PM            30,205 jetty-ajp-6.1.19.jar
26/07/2009  01:50 PM            21,585 jetty-rewrite-handler-6.1.19.jar
26/07/2009  01:50 PM            18,376 jetty-sslengine-6.1.19.jar
26/07/2009  01:50 PM            16,612 jetty-starter.jar
26/07/2009  01:50 PM           173,609 jetty-util-6.1.19.jar
26/07/2009  01:50 PM             4,899 jsp-2.1-jetty-6.1.19.jar
26/07/2009  01:50 PM         1,026,148 jsp-2.1.jar
26/07/2009  01:50 PM           134,855 jsp-api-2.1.jar
18/03/2010  05:22 PM           391,834 log4j.jar
18/03/2010  05:22 PM           822,794 lucene-core.jar
12/09/2007  09:45 PM           355,030 mail.jar
15/12/2007  07:27 PM            15,590 mailcheck.jar
18/03/2010  05:22 PM           447,999 metadata-updater.jar
29/03/2006  10:26 AM           148,179 mx4j-impl.jar
29/03/2006  10:26 AM           261,135 mx4j-jmx.jar
29/03/2006  10:26 AM           167,500 mx4j-remote.jar
29/03/2006  10:26 AM           491,164 mx4j-tools.jar
20/10/2005  04:00 PM            28,080 nielm_getrssnews.jar
04/12/2008  12:58 PM            47,019 nielm_sageimdb.jar
21/12/2007  10:46 PM            33,916 nielm_sagemenureader.jar
31/01/2010  09:32 AM            15,248 nielm_sageutls.jar
13/02/2010  01:11 PM           377,404 nielm_sagewebserver.jar
31/01/2010  09:32 AM            55,212 nielm_sagexmlinfo.jar
18/03/2010  05:22 PM           381,379 phoenix.jar
13/10/2008  10:46 PM            66,795 sagemc.jar
06/03/2010  05:17 PM           287,120 sageortus.jar
18/03/2010  05:22 PM           391,755 sagex.api.jar
29/03/2006  10:26 AM            89,764 sbbi-jmx-1.0.jar
04/05/2006  08:56 AM           109,503 sbbi-upnplib-1.0.3.jar
26/07/2009  01:50 PM           134,133 servlet-api-2.5-6.1.19.jar
04/12/2005  04:25 PM            31,789 servlet.jar
              51 File(s)     15,384,948 bytes

Now to check out all this new and wild stuff on TV Explorer ;-)

Bobby

[jreichen]

FYI, the wiki has a list of the jar files delivered with the various Jetty versions.

[jreichen]

Originally Posted by GKusnick

An issue has come up over in the Web Interface for Jetty thread about the use of the temp directory for WAR file deplyoment. The problem is that Windows Disk Cleanup Wizard and similar maintenance tools assume that files in the temp dir are safe to delete. This is not true of WAR deployments; deleting them breaks the associated web app.

Can we get Jetty to do its default deployments to someplace other than the temp dir, so that maintenance tools can run without breaking things? So far I've been manually editing the web app's context file to deploy elsewhere, but this has the unwanted side effect (on Windows) of breaking the hot-deploy feature.

I found the rules for temp directories. They seem overcomplicated and there's no one solution that is best for our needs.

The reason Slugger's method works when it comes to avoiding file locks is that it's the only one of all those cases that will attempt to delete the existing temp dir before extracting the new war file. If the delete fails it will create a random dir name and extract the war to that dir, although it appears to only do that on the first redeployment. That's only apparent by analyzing the code.

[tmiranda]

I'm making a first attempt at creating a servlet and have found some strange behavior that I do not understand. Thanks to stuckless I was finally able to create a small servlet that picks up an argument from the URL and displays a simple message in a browser. After changing the message, rebuilding the .war and copying the .war over to the webapp directory, the old message still appears. Even if I delete the .war file from the webapp directory the message appears. If I wait several hours after replacing the .war file the new message appears.

What's going on here? Does Jetty somehow cache the .war file? How can I get Jetty to pick up a .war file that I have updated? I was under the impression that I did NOT have to stop Sage (and Jetty) but could just replace the .war file on the fly.

So much to learn, so little gray matter ...

[razrsharpe]

@tmiranda - try using ctrl+f5 to fully refresh the page.... ie/firefox will cache pages so the load faster... and a normal refresh isn't enough sometimes to get the new content

[tmiranda]

I thought about that, but I put in different arguments and that did not change the behavior. i.e. the following give me the same behavior:

http://SERVER:8080/MyServlet/MyServlet?parameter=This

http://SERVER:8080/MyServlet/MyServlet?parameter=That

[jreichen]

You might be running into the file locking issue. Shut down Sage, install the new war file and restart Sage. There should be some info on that in this thread. I don't have time to go into details now but give that a shot and if you're still having trouble I can help you tonight.

[PosterBoy]

The inevitable question...

How significant is the port to Sage 7.0?

How significant will it be for some of the Jetty apps? (I use SageJobQueue, SageAlert, and the Jetty version of Nielms web site)

I am guessing you guys were given early access to 7.0 and hopefully got a jump on the task.

Thanks for the awesome work

Kent

[bialio]

Everything you use is ready and waiting for you. Just gotta plug it in, so to speak

[PosterBoy]

Wow awesome news. It sounds like Sage did a great job of including all of you in the 7.0 development process. I am envious that you guys got a preview but you certainly deserve it, and I am reaping the rewards!

Thanks

Kent

[jreichen]

Originally Posted by PosterBoy

The inevitable question...

How significant is the port to Sage 7.0?

For me or for you? For you it should be pretty easy. I worked on automating the migration to make it as easy as possible. When you update from the plugin UI it will preserve your current settings. And you're really going to like configuring it from within the SageTV UI. No more manually editing properties files (except for the SSL keystore for now)! I'm going to update the wiki with some details but I also want to do some more coding, and coding always seems to be higher on the list

Originally Posted by PosterBoy

How significant will it be for some of the Jetty apps? (I use SageJobQueue, SageAlert, and the Jetty version of Nielms web site)

Not difficult at all. They'll run as-is, but Slugger is working on integrating the first two more closely with the event handlers in the plugin system. There isn't much to change in nielms web interface. That's pretty much in maintenance mode anyway, with a few enhancements here and there.

Originally Posted by PosterBoy

I am guessing you guys were given early access to 7.0 and hopefully got a jump on the task.

Are you trying to get me in trouble?

Originally Posted by PosterBoy

Thanks for the awesome work

Kent

You're welcome

[jreichen]

I created a new thread over on the SageTV V7 Customizations forum. Please post any V7 questions over there.

Thanks!

[brandypuff]

I can't get this plug-in to work. Spent hours trying already.

I browse to http://localhost:8500/sagem/m/menu.jsp but no page shows. I don't see any Jetty stuff in the sagetv_0.txt log either so i don't think Jetty is working. I've followed the installation instructions at http://tools.assembla.com/sageplugins/wiki/JettyInstall precisely. However, i don't have jetty/lib, jetty/log or jettty/static directories which the instructions show should be there.

I am running SageTV 6.6 and want to run the mobile SageTV browser but it seems like Jetty isn't working. I am in Windows 7 x64.

What do i do next?

[jreichen]

When you extract the zip file, make sure to preserve the directory structure that was stored in the zip file. If not, you'll end up with all the files in the SageTV installation folder and won't have the required folder structure under jetty.

[brandypuff]

Yes, i made sure i di dthat. I also added the following to
the sage.properties file:

load_at_startup_runnable_classes=net.sf.sageplugins.webserver.StartServer; sagex.jetty.starter.Main

and changed jetty.port=8500 in the JettyStarter.properties file

that should be all i need but when i restart the sagetv server, i can't access the url http://localhost:8500/

i don't see any file in the C:\Program Files (x86)\SageTV\SageTV\jetty\logs
directory either.

What could be wrong?

[jreichen]

Did you download SageWebserverSetup_2_25.exe, webserver_2_25.zip, or nielm_websrv_jetty_2_25.zip?

[brandypuff]

i have been running Neilm's Webserver (not the jetty version) Ok for several months.

What i tried is this:

I installed a fresh copy of the SageTV Media Center V6 on a clean system. Then I installed the Jetty plugin and the SageWebApp_1_2.zip app following instructions for install. It worked and browsing to http://localhost:8500/ shows:

/sagem ---> org.mortbay.jetty.webapp.WebAppContext@1be4777{/sagem,C:\Program Files\SageTV\SageTV\jetty/webapps/SageWebApp.war}
/ ---> org.mortbay.jetty.handler.ContextHandler@9ff0a8{/,file:/C:/Program%20Files/SageTV/SageTV/jetty/static}

So i zipped the clean JAR and Jetty directories and replaced the current directories on my Sage Server with these directories which contain the clean install. I restarted Sage Server and still, i can't connect to localhost:8500.

So, for some reason, the Jetty server is not starting on my Sage server. Have no idea why.