Jetty Web Server v3 released - plus more

[emveepee]

Originally Posted by jusjoken

Likely. The effort and amount of change from an old jetty 6 version to jetty 9 was already a lot to take on (one thing I read said it was about 43 version equivalents given how they use versions). It also is the last Jetty version to support Java 8 so given the age of many plugins I think it was a logical step.

I will consider updating jetty after I get a few other projects completed unless someone decides to take it on.

K

Thanks for the info I don't really know how SageTV works but I will see if I can get SRE to run, unlikely but worth a shot if I can help.

[jusjoken]

Originally Posted by emveepee

Thanks for the info I don't really know how SageTV works but I will see if I can get SRE to run, unlikely but worth a shot if I can help.

Is SRE no longer working?

SkiingWiz had updated it for jetty 9

[emveepee]

Originally Posted by jusjoken

Is SRE no longer working?

SkiingWiz had updated it for jetty 9

It does but I run an instance of Jetty with SRE on a $2 a month VPS for NextPVR users who don't have SageTV installed. I right away mitigated log4j but rather then upgrading to 9 I was hoping to use a supported version

[cat6man]

hi folks

i'm a little late jumping on this but i could use some help here on a now old topic.
i delated all the recommended stuff, except for WAR files, under webapps.

i'm not sure though what JAR files i may need to delete and my JAR files list is attached.
help would be much appreciated here.

thanks again for you all still keeping sage alive and kicking.

[jusjoken]

Originally Posted by cat6man

hi folks

i'm a little late jumping on this but i could use some help here on a now old topic.
i delated all the recommended stuff, except for WAR files, under webapps.

i'm not sure though what JAR files i may need to delete and my JAR files list is attached.
help would be much appreciated here.

thanks again for you all still keeping sage alive and kicking.

The JARs list looks fine (there are a few google-oauth-client jars that have jetty in the name that I am not familiar with so not sure what they are for or if they would cause an issue).

Could you describe the issue and post the sagetv_0.txt log as well as the logs/jettystarter.log file for me to review.

Thanks
K

[cat6man]

Originally Posted by jusjoken

The JARs list looks fine (there are a few google-oauth-client jars that have jetty in the name that I am not familiar with so not sure what they are for or if they would cause an issue).

Could you describe the issue and post the sagetv_0.txt log as well as the logs/jettystarter.log file for me to review.

Thanks
K

The problem is that in SRE, i get the red icon on all future baseball games that are scheduled, as if if couldn't confirm the SRE monitoring.

log files attached.

also, in my list of JARs, i see a few that were recommended to be removed in older posts.
specifically,
commons-io-2.4.jar
commons-jxpath-1.1.jar
gson-1.7.1.jar
jcifs-1.1.6.jar
sbbi-upnplib-1.0.3.jar
perhaps not a problem, but thought i'd mention them.

[jusjoken]

Originally Posted by cat6man

The problem is that in SRE, i get the red icon on all future baseball games that are scheduled, as if if couldn't confirm the SRE monitoring.

log files attached.

also, in my list of JARs, i see a few that were recommended to be removed in older posts.
specifically,
commons-io-2.4.jar
commons-jxpath-1.1.jar
gson-1.7.1.jar
jcifs-1.1.6.jar
sbbi-upnplib-1.0.3.jar
perhaps not a problem, but thought i'd mention them.

The jars you listed here are fine I think. I have newer versions the following 2 in my system...

commons-io-2.4.jar - I have commons-io-2.5.jar
gson-1.7.1.jar - I have gson-2.7.jar

Not sure if either of those would cause issues with SRE.

The Jetty logs indicate that Jetty and all the web plugins including SRE loaded correctly with NO errors.

I also see in the sage logs that SRE is doing things...but I do not use SRE so cannot be sure what to expect in the logs for SRE.

I suggest you post in the SRE plugin thread and pm SkiingWiz who maintains it and see if he can understand the issue you are seeing.

K

[cat6man]

thanks K

[Galaxysurfer]

@cat6man That sound's like my response to my Dad. I guess their tinkering was where we got the bug to do this with SageTV etc.

[alfi33]

I upgraded Jetty and the web apps that I had installed. All seems to be working fine except for the http://<IP>:8090<PORT>/bmt/#status page for BMT. This page will load but clicking on any menu item will make it unresponsive and it eventually times out.

If I go directly to http://<IP>:8090<PORT>/bmt/#browse or #configure, it all works great and is very responsive. The menu items work fine from these pages...except if I click on the Status menu item which will makes it hang again.

The other web apps (SageTV Web Interface and Mobile Web Interface) both seem to be working fine.

I've uninstalled/reinstalled the BMT Web Interface.
I've cleaned out folders from jetty/webapps
I've cleaned out several old jars as suggested earlier in this thread.

Any ideas?

[jusjoken]

There are numerous file exceptions in the log...for instance..

opt/sagetv/server/ChannelLogos/KZJODT.png

Not sure is this is related but the channel logos are being searched for but failing.

k