Plugin: Jetty Web Server 2.0

[Slugger]

Originally Posted by Fonceur

Sure, they know that in service mode, when they do a restart they are only restarting the UI, not the service itself, which is useless... Why they haven't fixed it since I brought it up 6+ months ago, I don't know...

I don't see this behaviour. A Sage triggered restart of my server (in service mode, on WinXP Home 32bit SP3) does completely restart the entire Sage server service. Jars always update/cleanup/etc. with this action. Are you on something newer than XP? 64bit? That might be the issue or I'm just lucky.

[Fonceur]

Originally Posted by Slugger

I don't see this behaviour. A Sage triggered restart of my server (in service mode, on WinXP Home 32bit SP3) does completely restart the entire Sage server service.

I've just updated 3 plugins, and indeed everything went fine. So I guess it's not as systematic as when I originally reported it.

[nyplayer]

Originally Posted by jreichen

Sure. It's hard to know how much detail to go into

What to Look For
I'll start by answering your second question. That's probably what most people care about. There aren't any special steps for users. After you update Jetty and restart Sage, ant-1.6.5.jar should no longer exist in the JARs folder and there should now be an ant.jar file.

What Happens During the Update
Versions of the Jetty before 2.3.0 were delivered with an Ant file named ant-1.6.5.jar. That file has been removed in Jetty 2.3.0 and a dependency has been placed on the new Ant library plugin instead. When you upgrade Jetty to 2.3.0, it uninstalls the old version of the Jetty plugin including removing ant-1.6.5.jar from the JARs folder. Then it installs the new version of the Jetty plugin. But first it checks to make sure all dependencies are installed. Since there's a new dependency on this Ant library (which just has the ant.jar), that is installed before the new version of Jetty.

What is Ant?
Ant is a platform-neutral XML- and Java-based build tool. Jetty uses it to compile JavaServer Pages (JSP) into servlets when a page is first requested. The servlets actually generate the pages, not the JSPs, but JSPs make it easier for developers to write the user interface of a web app. Ant is an Apache project that's used in a lot of projects but up until now no other Sage plugins have used it.

Why This Matters
I had a request from Slugger to move it to a library so he could use it in another plugin. If his plugin (not yet released) were to be installed before Jetty is updated - or if I didn't make this change - then you'd end up with two copies of Ant in your JARs folder, and that's never a good thing. That's why we decided to do this as soon as possible to give users a chance to update Jetty and limit the possibility of that happening.

Jason

This messed up the Metadata tools they look for 1.65 Ant. It was the commons-codec that complained about missing ant 1.6.5 jar. I completely removed all my plugins... reinstalled now everything seems ok.


PS this also caused my Sagetv server to become unstable until I removed and reinstalled all my plugins. My recordings were being interrupted and broken up into pieces. Screen Cap attached.

[ptzink]

Well, I manually shut down the SageTV service. Then I went to Task Manager to make sure there were no "sagetvservice.exe"s running (that has been know to happen from time to time ). Then I restarted the service. There are still both the ant-1.6.5.jar and the ant.jar files in the JARs folder. From the sounds of it, maybe I am glad they are both still there, since I use BMT a lot. Also, it appears my issues earlier were related to my internet/cache situation. Everything seems fine when browsing locally now.

[Fonceur]

Originally Posted by ptzink

Then I went to Task Manager to make sure there were no "sagetvservice.exe"s running (that has been know to happen from time to time ).

Typically, the proper way to shutdown the service is by launching SageTVService.exe from the SageTV menu and pressing stop...

[Slugger]

Originally Posted by nyplayer

This messed up the Metadata tools they look for 1.65 Ant. It was the commons-codec that complained about missing ant 1.6.5 jar. I completely removed all my plugins... reinstalled now everything seems ok.


PS this also caused my Sagetv server to become unstable until I removed and reinstalled all my plugins. My recordings were being interrupted and broken up into pieces. Screen Cap attached.

The commons-codec plugin does not provide the ant-1.6.5.jar. The error message is either a false positive or a sign that your filetracker.properties file was corrupted. Either scenario would probably prompt me to open a bug report with SageTV. Uninstalling and reinstalling all your plugins would, presumably, address the latter scenario, if that were indeed the issue.

Originally Posted by ptzink

Well, I manually shut down the SageTV service. Then I went to Task Manager to make sure there were no "sagetvservice.exe"s running (that has been know to happen from time to time ). Then I restarted the service. There are still both the ant-1.6.5.jar and the ant.jar files in the JARs folder. From the sounds of it, maybe I am glad they are both still there, since I use BMT a lot. Also, it appears my issues earlier were related to my internet/cache situation. Everything seems fine when browsing locally now.

You do not want both jars present in your JARs directory. Nothing good will come of such a scenario. I don't know why both remain after a complete SageTV restart, but running SageTV with both jars present in that directory will inevitably lead to issues (with the plugins that use the ant jar file). You may want to open a support ticket with Sage to address why the plugin manager isn't cleaning up the old ant-1.6.5.jar file. Either way, you never want both present.

[Skirge01]

Originally Posted by Slugger

I don't see this behaviour. A Sage triggered restart of my server (in service mode, on WinXP Home 32bit SP3) does completely restart the entire Sage server service. Jars always update/cleanup/etc. with this action. Are you on something newer than XP? 64bit? That might be the issue or I'm just lucky.

My client PC is on 64-bit Windows 7 Home Premium and the server is WHS v1. I will say that it sometimes works, so maybe there's something different between the plugins. I'll have to try and take notice each time it happens.

[ptzink]

Okay, I have rebooted the entire server and still have both JAR files. Is it safe to just rename the old file to a .bak or will that not remedy the issue (or cause other issues)? I want to make sure I don't screw anything up but I also don't want to make things more difficult than they have to be.

[DIBU]

Hi, after update i will become this error:

Exception while processing servlet:
java.lang.reflect.InvocationTargetException: Exception while executing SageApi: "GetShowSeasonNumber" numargs=1
java.lang.reflect.InvocationTargetException: Exception while executing SageApi: "GetShowSeasonNumber" numargs=1
at net.sf.sageplugins.sageutils.SageApi.Api(SageApi.java:20)
at net.sf.sageplugins.webserver.Airing.printAiringTableCell(Airing.java:291)
at net.sf.sageplugins.webserver.HomeServlet.doServletGet(HomeServlet.java:374)
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.HandlerCollection.handle(HandlerCollection.java:114)
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.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)
Caused by: java.lang.reflect.InvocationTargetException
at sage.SageTV.api(Unknown Source)
at net.sf.sageplugins.sageutils.SageApi.Api(SageApi.java:17)
... 24 more
Caused by: sage.a.e: Error in method reflection of GetShowSeasonNumber of java.lang.NullPointerException
at sage.e$e.a(Unknown Source)
at sage.e.a(Unknown Source)
... 26 more
Caused by: java.lang.NullPointerException
... 28 more

[Slugger]

Originally Posted by ptzink

Okay, I have rebooted the entire server and still have both JAR files. Is it safe to just rename the old file to a .bak or will that not remedy the issue (or cause other issues)? I want to make sure I don't screw anything up but I also don't want to make things more difficult than they have to be.

Probably, but I'm not SageTV support so I can't make that statement with 100% certainty. If it were my system, I'd make sure Jetty reports itself as the latest version in the plugin manager, stop SageTV completely, delete the ant-1.6.5.jar, make sure the ant.jar file is still there and restart SageTV.

Again, I'm not SageTV support so following the above paragraph may or may not work for you. It may or may not cause more/new problems. I also have a full backup image of my SageTV directory I can restore should I run into problems, making me a little more brave in such situations.

[ptzink]

Originally Posted by Slugger

Probably, but I'm not SageTV support so I can't make that statement with 100% certainty. If it were my system, I'd make sure Jetty reports itself as the latest version in the plugin manager, stop SageTV completely, delete the ant-1.6.5.jar, make sure the ant.jar file is still there and restart SageTV.

Again, I'm not SageTV support so following the above paragraph may or may not work for you. It may or may not cause more/new problems. I also have a full backup image of my SageTV directory I can restore should I run into problems, making me a little more brave in such situations.

Sage plugin manager says Jetty Web Server v. 2.3.0.14 as does the web apps page. I have submitted a bug report to Sage and will wait for their feedback on this issue. Thanks for the reply.

[Fonceur]

Originally Posted by DIBU

java.lang.reflect.InvocationTargetException: Exception while executing SageApi: "GetShowSeasonNumber" numargs=1

Sounds like you are not using the SageTV beta, but the web server is trying to make a call to a new function from the beta...

[DIBU]

Originally Posted by Fonceur

Sounds like you are not using the SageTV beta, but the web server is trying to make a call to a new function from the beta...

uh thats right..hmm it is also bad

[jreichen]

You get that error after updating Jetty? Did you also update the SageTV Web Interface plugin? What version of the web interface are you running?

[ptzink]

I submitted a bug report to Sage RE: Duplicate JARs and they said:

If there's a reproducible case of this please ask the plugin devs to submit
a bug report on it so we can look into it.

Let me know if/what you need of me.

[ptzink]

Well, I decided to go ahead and shut down Sage, rename the old jar file, and move it out of the SageTV directory. I kept it around in case I should need it for something. I have restarted Sage and everything looks fine as far as I can tell.

[DIBU]

Originally Posted by jreichen

You get that error after updating Jetty? Did you also update the SageTV Web Interface plugin? What version of the web interface are you running?

V 2.30

[wayner]

One thing that I would find useful is in some of the EPG views on the web pages if you could click on the TV Station logo/name and go to the web page of the TV station/network. You could by default try to guess the web page (ie for WKBW you would try www.wkbw.com) but the user would have the option of changing the URL if the default didn't work.

This would be especially useful for me as one channel, Setanta Sport, often seems to send incorrect data to Zap2it and I have to go and set up manual recordings after checking the TV schedule on the station's web site. But I am sure that others would also find this of use.

Perhaps this could also be done with TV/movie show titles.

[tmiranda]

I just updated to the latest Jetty (2.3.0.14) and it also left the ant-1.6.5.jar in the JARs directory. The update did not produce any errors.

[Slugger]

If you had a restore point of your system that you could go back to and then reproduce this for Sage support then maybe they could figure out the bug in the plugin manager. I was never able to reproduce this bug myself.