Plugin: Jetty Web Server 2.0

[thomaszoo]

Just as oddly as it stopped working, it has started working again. I have InfoPopup / Caller ID installed and noticed last night that it did not work for the first call that came in after uninstalling and reinstalling all of the plugins. Then it started working on the next call. So tonight I figured why not see if the webserver is also working now and yes it is! So either the steps I went through to trouble shoot fixed it or it was caused by sunspots / aliens / ? and may or may not reappear!

Regardless, thanks for the great plugins. I really missed the mobile webserver on my phone.

Wayne

[Keo]

As part of external access you need to chang the ID and PW. I change the ID and PW and now I keep getting my ID or password is invalid. I am 100% sure I got it correct. I try it going directly to the IP, and get the same result.

What am I doing wrong here?

[jreichen]

Make sure you restart Jetty. There's a button to restart it on the same screen where you change the user and password.

[jnmfox]

I am attempting to change my Internet Connection but when I do I get the following message:
There was an eroor setting the plugin configuration value of: java.lang.illegalStateException: No UPnP device selected.

TiA!

[jreichen]

Make sure you enable UPnP by setting up the Placeshifter Internet connection in Setup->Detailed Setup->Server->Configure Placeshifter Internet Connection.

[brewston]

Hi

I recently upgraded to Sage 7 but previously had the mobile web server running on v6. I installed 2.0 from the plugin manager and have noticed that the 'Now playing' section only reports recorded (or live) TV I'm sure it used to report imported videos too. Did something change ? Alternatively, can I clear our all the old config and re-install ? (In case something left over from v6 install is causing this)

Thanks

[pjpjpjpj]

Originally Posted by brewston

Hi

I recently upgraded to Sage 7 but previously had the mobile web server running on v6. I installed 2.0 from the plugin manager and have noticed that the 'Now playing' section only reports recorded (or live) TV I'm sure it used to report imported videos too. Did something change ? Alternatively, can I clear our all the old config and re-install ? (In case something left over from v6 install is causing this)

Thanks

This is really a question for the Mobile Web server thread, but, yes, with the newest version (you can tell most easily if it's gray to match v7, rather than blue to match v6), there is only access to the recordings. You can, with the new version, watch streaming recordings, which I don't think the mobile version used to do.

I still have access to the "web server" (not mobile) on my iPod Touch and can access the old version, which has a webremote for extenders and can access all my media - but I can't stream video on the iPod because none of the "external player" types are compatible.

[brewston]

Ah yes, I can see I picked the wrong thread now. I will post there, thanks

[jreichen]

As I mentioned on the previous page of this thread. I'm releasing update 2.2.1 that makes a minor change to Jetty's logging so those of you who have submitted logs where Jetty didn't write anything to the log should now see the messages.

[alucas1966]

Hi, I was troubleshooting the plugin as it wasnt operating for some reason, whilst doing the update to the most recent version I have managed to mess up the password.
I deinstalled and reinstalled but I still cant change this, I'd appreciate some direction.

Thanks in advance.

[jreichen]

The user and password are stored in the SAGE_HOME/jetty/etc/realms.properties file. If the file is modified after it's installed (i.e. you change your user or password, then the file is not removed by the uninstall. This is standard behavior for the Sage plugin uninstaller.

You can either manually edit that file and restart Sage (restarting Jetty from the plugin's configure menu should work, too) or uninstall the plugin, manually delete the file, and reinstall the plugin.

[jreichen]

Version 2.3.0 is now available. This is a minor update that doesn't ship its own Ant jar file anymore. There's a new Ant library dependency that can be shared with other plugins. It's recommended that you take this update to avoid any classpath problems once other plugins use the Ant library.

• Remove Ant JAR from this download and instead rely on the Ant plugin dependency

[pjpjpjpj]

Originally Posted by jreichen

Version 2.3.0 is now available. This is a minor update that doesn't ship its own Ant jar file anymore. There's a new Ant library dependency that can be shared with other plugins. It's recommended that you take this update to avoid any classpath problems once other plugins use the Ant library.

• Remove Ant JAR from this download and instead rely on the Ant plugin dependency

This morning I saw (on my extender) a plugin update notification. I went in and just clicked "update". Can you explain (for dummies like me) what the whole "Ant JAR" thing means - or, specifically, if I updated the plugin via extender and I want to be future-proofed as you explain, what I need to do?
Thanks!

[jreichen]

Originally Posted by pjpjpjpj

This morning I saw (on my extender) a plugin update notification. I went in and just clicked "update". Can you explain (for dummies like me) what the whole "Ant JAR" thing means - or, specifically, if I updated the plugin via extender and I want to be future-proofed as you explain, what I need to do?
Thanks!

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

[ptzink]

Originally Posted by jreichen

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

After the update and a restart I see both the ant-1.6.5.jar and the ant.jar files. Is that a bad sign? Should I manually delete the ant-1.6.5.jar file? The reason I ask is that my access to the Sage Web Apps (at least remotely) are acting strangely (images not loading sometimes. sometimes pages don't load). This could also just be my current connection (work connection that goes flaky sometimes) and unrelated to Jetty as well.

[jreichen]

Can you try manually restarting Sage and see if that cleans up the JARs?

[Skirge01]

I just upgraded and both are still on my server, as well. I went in and manually deleted it and everything still seems to be working. I did notice that the SageTV client (where I did the server install from) didn't end itself gracefully and I had 4 SageTV exe's running.

[jreichen]

I just saw that Fonceur posted this over in the mobile web interface thread:

The problem is that if you are running in service mode, the built in restart in SageTV 7 doesn't actually work properly and you still need to force a proper restart...

That might explain why this worked fine for me on Linux.

[Skirge01]

Would explain the extra Sage exe's on my client, though? Now, is this a bug that Sage is aware of?

[Fonceur]

Originally Posted by Skirge01

Now, is this a bug that Sage is aware of?

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