Plugin: Jetty Web Server 2.0

[razrsharpe]

Originally Posted by tmiranda

Going from memory, that API returns the latest version that is available in the repository, not the installed version. I think I had to write some custom java code to ge tthe version that was actually installed. It's been a while so don't take my word on that.

Tom

imho there should really be two api calls. GetPluginVersion (current available version on the manifest) and GetPluginInstalledVersion (version installed on the client).... writing custom code/parsing you really shouldn't need to do to get the installed and available version

[jreichen]

Version 2.2 will be available shortly. It includes a few minor things, including a fix for misreported versions on the /apps page that was reported by voorhees and razrsharp.

• Minor apps web page formatting changes
• Add user to the 'user' role if none specified in realm.properties
• Fix displayed version of installed plugin

Jason

[jorton]

I hope this is the right place to ask this...

I upgraded both the Jetty Web Server 2.x and the Mobile Web Interface V2 iOS Streaming plugins last night and now it seems as if I can't connect to the web server.

I have used the following address for months to connect,

http://mediaserver:8080/apps/

Any place I should start to look?

Since I see "Powered by Jetty://" it looks like the server is running, just not showing the "apps"

This is the error in the jetty request log,

192.168.0.192 - - [16/Jan/2011:15:53:47 +0000] "GET /apps/ HTTP/1.1" 404 1273 "-" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C)"

Thanks,

Jeremy



Update: I tried uninstalling all web related plugins (BMT, jetty,Sagetv web, Sagetv mobile web) then deleting the sagetv/jetty folder and reintstalling, after the reinstall the apps showed but there was an error on BMT, I restarted the jetty server from the config screen and then things went back to the 404 error above.

[jreichen]

It sounds similar to the problem with deleting directories in the jetty/webapps directory that was fixed in 2.1.0.

Can you print a directory listing of jetty/webapps while Sage is running, then shut down Sage and print another directory listing, then start Sage again and print the directory listing again? I'd like to see if the directory is being recreated and, if not, what files might be preventing it.

[jorton]

Originally Posted by jreichen

It sounds similar to the problem with deleting directories in the jetty/webapps directory that was fixed in 2.1.0.

Can you print a directory listing of jetty/webapps while Sage is running, then shut down Sage and print another directory listing, then start Sage again and print the directory listing again? I'd like to see if the directory is being recreated and, if not, what files might be preventing it.

I just went to print the directory like you requested and everything is working... I didn't do anything other than restart the server for another plugin... Didn't mean to waste your time, sorry. If if happens again I'll print off the directory listing and attach.

J

[LehighBri]

Originally Posted by jreichen

It sounds similar to the problem with deleting directories in the jetty/webapps directory that was fixed in 2.1.0.

Can you print a directory listing of jetty/webapps while Sage is running, then shut down Sage and print another directory listing, then start Sage again and print the directory listing again? I'd like to see if the directory is being recreated and, if not, what files might be preventing it.

I'm having the same problem. Here is the directory after I delete the expanded directories and before I start SageTV:

Directory of C:\Program Files\SageTV\SageTV\jetty\webapps

01/16/2011 07:27 PM <DIR> .
01/16/2011 07:27 PM <DIR> ..
01/15/2011 02:54 PM 21,229 apps.war
01/09/2011 06:47 PM 4,750,123 bmt.war
01/15/2011 10:40 PM 9,415,022 MediaStreaming.war
07/18/2010 08:37 PM 1,316,134 nielm_sagewebserver.war
11/07/2010 07:44 PM 2,466,953 SageWebApp.war
5 File(s) 17,969,461 bytes
2 Dir(s) 53,046,358,016 bytes free

And here is the directory after I start SageTV (note everything was working fine before I updated my jetty plugin to the latest version):

Directory of C:\Program Files\SageTV\SageTV\jetty\webapps

01/16/2011 07:29 PM <DIR> .
01/16/2011 07:29 PM <DIR> ..
01/16/2011 07:29 PM <DIR> apps
01/15/2011 02:54 PM 21,229 apps.war
01/09/2011 06:47 PM 4,750,123 bmt.war
01/16/2011 07:29 PM <DIR> MediaStreaming
01/15/2011 10:40 PM 9,415,022 MediaStreaming.war
01/16/2011 07:29 PM <DIR> nielm_sagewebserver
07/18/2010 08:37 PM 1,316,134 nielm_sagewebserver.war
01/16/2011 07:29 PM <DIR> SageWebApp
11/07/2010 07:44 PM 2,466,953 SageWebApp.war
5 File(s) 17,969,461 bytes
6 Dir(s) 53,046,562,816 bytes free

For some reason I don't see a bmt folder but I see folders for all other war files. Thoughts on additional debugging I can do here?

[DarkWolf77]

Originally Posted by acrowe

Correct. Jetty Plugin 2.0.1.19


I tried on my other machine (also a mac running the same version of placeshifter (6.2.2), OS (10.6.4), etc) with the same results. The only windows machine I have here is the sage server itself. However I can probably install on work and try placeshifter remotely.


Correct.


See attached.
sage_1 is when you first click the plugin
sage_2 is when you click on another plugin
sage_3 is after you move up and down in the menu


I wasn't, but will try via the properties file now and post that.

Hey, seeing that the guy that had this issue resolved it by reinstalling from scratch, I thought I'd post the solution to this issue, since I was also having it: mainly, when selecting the Jetty server in the plugin screen to get to the configuration, getting a strange windowless menu (with only "close" and "configure" appearing and being unselectable) and/or sage hanging.

I found through the use of the BMT plugin that I for some reason had a very old version of the sagex-api loading instead of the v7 one in the JAR directory--it being left over from an older install of (I think) neilm's webserver. Once I removed that and the newest version of the jar loaded, and everything started working fine.

[jreichen]

Originally Posted by LehighBri

I'm having the same problem. Here is the directory after I delete the expanded directories and before I start SageTV:

That's great but I didn't want you to manually delete the directories It should be doing that automatically when Sage shuts down (but the file-locking issue sometimes prevents it). If not, when Jetty plugin 2.1 or later starts up it should clean them up. If for some reason that doesn't work I added a fallback so it uses a directory with _1, _2, etc appended.

[LehighBri]

Originally Posted by jreichen

That's great but I didn't want you to manually delete the directories It should be doing that automatically when Sage shuts down (but the file-locking issue sometimes prevents it). If not, when Jetty plugin 2.1 or later starts up it should clean them up. If for some reason that doesn't work I added a fallback so it uses a directory with _1, _2, etc appended.

I should have updated you, but I just ended up uninstalling all web app plugins that used Jetty, uninstalled the Jetty web server plugin, then reinstalled Jetty web server plus all of the plugin web apps and things work just fine now. No clue what the issue was but I'm back in action.

[jreichen]

Thanks for the update. If anyone else has problems like this let me know and I'll see if I can find the cause.

[AlphaCrew]

I noticed that SageAlert was no longer working, so I went to check it out, and noticed that I'm having the exact same problem as above (jorton).

I have restarted the entire machine, but still no dice. I'm currently recording some shows, so I don't want to go messing around right now, but any suggestions would be great.

[KJake]

Same issue here - the only context left after the update is /sagex - all others are gone (sage, sagem, apps, bmt). I've restarted Sage already too.

[jreichen]

Originally Posted by AlphaCrew

I noticed that SageAlert was no longer working, so I went to check it out, and noticed that I'm having the exact same problem as above (jorton).

I have restarted the entire machine, but still no dice. I'm currently recording some shows, so I don't want to go messing around right now, but any suggestions would be great.

Can you go through the instructions I gave him for printing directory contents?

[jreichen]

Originally Posted by KJake

Same issue here - the only context left after the update is /sagex - all others are gone (sage, sagem, apps, bmt). I've restarted Sage already too.

What's in the jetty/contexts directory? Can you submit a log?

[KJake]

apps.xml
bmt.xml
mediastreaming.xml
nielm_websrv.context.xml
sagewebapp.xml
sagex.xml

Good call on the log, bet this is a problem

Wed 1/19 1:02:30.399 [SageTV@1a16869] LOADED PLUGINS=[SageTVPlugin[dom4j state=Failed name=dom4j version=1.6.1 type=Library desc=SageTV Dependency JAR Plugin for dom4j-1.6.1.jar - no need to download directly author=stuckless screenshots=null videos=null modified=4/10/2010 installed=11/9/2010 resPath= webpages=null implementation= desktopOnly=false serverOnly=false OS=Win,Linux,Mac dependencies=null packages=null], SageTVPlugin[sage-diamond-api state=Failed name=Sage Diamond API version=1.01 type=Library desc=Diamond UI API- Do not install directly just a dependency!! author=PluckyHD screenshots=null videos=null modified=11/9/2010 installed=12/11/2010 resPath= webpages=null implementation= desktopOnly=false serverOnly=false OS=Win,Linux,Mac dependencies=[PluginDependency[sagex-api minVer=7.0.7.0 type=Plugin]] packages=null], SageTVPlugin[osdclockplaytime state=Failed name=OSD Clock and Play Time version=1.3.1 type=STVI desc=SageTV STVI Plugin for displaying clock and/or how long current media has been playing author=toricred screenshots=null videos=null modified=5/29/2010 installed=6/13/2010 resPath= webpages=null implementation= desktopOnly=false serverOnly=false OS=Win,Linux,Mac dependencies=null packages=null], SageTVPlugin[novolonosd state=Failed name=Hide Volume Area from OSD version=0.1.1 type=STVI desc=This plugin will hide the volume icon and slider form the media player on screen display (OSD).  This plugin is particularly useful for users who have set up their remote to control volume through a different source (eg. A/V receiver) and do not have SageTV control the volume. author=pvrpenguin screenshots=[http://dl.dropbox.com/u/7563789/sagetv/removeVolumeArea/screenshot.png] videos=null modified=6/19/2010 installed=6/19/2010 resPath= webpages=null implementation= desktopOnly=false serverOnly=false OS=Win,Linux,Mac dependencies=null packages=null], SageTVPlugin[directvusachannellogo state=Failed name=DirecTV-USA Channel Logo Pack version=0.0.3 type=Images desc=A collection of channel logos for DirecTV's USA lineup. The intention is to create seaparate packs for local channels. author=bcjenkins screenshots=null videos=null modified=5/20/2010 installed=6/23/2010 resPath= webpages=null implementation= desktopOnly=false serverOnly=false OS=Win,Linux,Mac dependencies=null packages=null], SageTVPlugin[nielm_autoaspect state=Failed name=nielm_autoaspect version=1.3.1 type=Library desc=SageTV Dependency JAR Plugin for nielm_autoaspect.jar - normally no need to download directly author=nielm, JREkiwi screenshots=null videos=null modified=10/21/2010 installed=10/22/2010 resPath= webpages=[http://forums.sagetv.com/forums/showthread.php?t=49358] implementation= desktopOnly=false serverOnly=false OS=Win,Linux,Mac dependencies=[PluginDependency[sageutls minVer=1.4.1 type=Plugin], PluginDependency[sagex-api minVer=7.0.19.0 type=Plugin]] packages=null], SageTVPlugin[jetty state=Enabled name=Jetty Web Server version=2.2.0.9 type=Standard desc=Provides a platform for SageTV web application plugins.

The whole thing is attached.

[edit]
in my JARs directory, I have a dom4j-1.6.1.jar, dated 4/10/2010
[/edit]

[jreichen]

The contexts directory looks ok.

Thanks for the log. I don't see much besides what you pointed out. Would you mind turning on Jetty's logging by going to the Jetty Web Server in the plugin manager, choosing to configure the plugin, setting the log level to VERBOSE, then restarting Sage?

That will output a lot more about what Jetty is doing and may help shed more light on the issue.

[KJake]

All set:

jetty/jetty.configfiles="C\:\\Program Files\\SageTV\\SageTV\\jetty/etc/jetty.xml"
jetty/jetty.home=C\:\\Program Files\\SageTV\\SageTV\\jetty
jetty/jetty.log.level=VERBOSE
jetty/jetty.logs=C\:\\Program Files\\SageTV\\SageTV\\jetty\\logs

Restarted, reattached.

[jreichen]

I don't see anything odd other than those plugins at failed status. Are any of your plugins disabled?

[KJake]

Originally Posted by jreichen

I don't see anything odd other than those plugins at failed status. Are any of your plugins disabled?

Nope, everything is Enabled (or it doesn't have an option).

[jreichen]

Congrats on your 1000th post. I beat you by 2

I'll have to look at this from home. I should be seeing more info in the log if something is failing.