Plugin: Sage Recording Extender (SRE)

[Slugger]

Snapshot 739 now available... contains lots of little GUI fixes/enhancements; no changes to the monitor engine (nor do I expect any changes to the engine between now and official v2.4.0).

[Sparhawk6]

I'm getting the following error when I try to create an override:

JSON response error: Could not initialize class com.google.code.sagetvaddons.sre.server.WebReader (500)

Using the latest build, 739. Any ideas?

[Slugger]

Originally Posted by Sparhawk6

I'm getting the following error when I try to create an override:

JSON response error: Could not initialize class com.google.code.sagetvaddons.sre.server.WebReader (500)

Using the latest build, 739. Any ideas?

I'm seeing some issues with the override interface, but not the exact one you mention above. There are definitely some issues I need to address, but not tonight. What exactly were you doing when this error occurred? Was it creating the override in the table or did that succeed then when you tried to add it to the global map online did that fail? Did you have Jetty debug logging on? If so, do you have the exception dump handy? If not, I'd really appreciate it if you turned on Jetty debug logging and logged that exception and provided it to me.

[spacecadet]

Originally Posted by spacecadet

Will let you know how it goes with tonight's game!

So the BSU/TCU game ended early, so there was no need for SRE to extend the broadcast. However, I noticed this morning that SRE "crashed" at the end of this game. Not sure what the issue might be.

The last run of SRE was at 2010-01-04 21:50:30,604 and it hasn't run since. I'm assuming that deleting the sre.sqlite file and restarting will resolve the issue (although I haven't tried this yet).

2010-01-04 21:50:21,448 INFO  [WorkerMaid]: Stopping worker!
2010-01-04 21:50:21,448 INFO  [SageRecordingExtender]: Sleep interrupted
2010-01-04 21:50:21,448 INFO  [SageRecordingExtender]: Found 2 active recordings.
2010-01-04 21:50:21,448 INFO  [AiringMonitorFactory]: MythBusters:  --> No monitor due to orig air date violation
2010-01-04 21:50:21,448 INFO  [SageRecordingExtender]: 	MythBusters:  --> No monitor
2010-01-04 21:50:21,448 INFO  [SageRecordingExtender]: 	College Football: Tostitos Fiesta Bowl: Boise State vs. Texas Christian --> Too early to check status
2010-01-04 21:50:23,417 INFO  [WorkerMaid]: Starting worker!
2010-01-04 21:50:30,557 INFO  [DataStore]: Reading data store from 'C:\Program Files\Frey Technologies\SageTV\sre.sqlite'
2010-01-04 21:50:30,589 INFO  [SageRecordingExtender]: Found 2 active recordings.
2010-01-04 21:50:30,604 INFO  [AiringMonitorFactory]: MythBusters:  --> No monitor due to orig air date violation
2010-01-04 21:50:30,604 INFO  [SageRecordingExtender]: 	MythBusters:  --> No monitor

[Slugger]

I need exception dumps. You need to enable SageTV logging and Jetty debug logging in order to log the exceptions. Without the exceptions all I know is that SRE stopped, but I have no idea why. I also need to know what build you're running. If you're not running the latest one available then please upgrade and try to reproduce the problem. (However, don't bother with 739, it needs some work done to it, which I'm doing right now.)

[Slugger]

Everyone should move to snapshot 741. For those that were having problems please try to reproduce the problem and if you're able to, I really need to see the exception dumps in the Jetty debug logs along with as much details as possible on how to reproduce the error. 741 fixes a bunch of problems with the global override map editor.

The sre-maps app logs showed that someone was trying to monitor last night's Alabama/Texas game with a 2.4.0 beta older than 737. This is a friendly reminder that you must be running build 737 or later - all versions prior to 737 will not work with the current version of the sre-maps app.

Please move to 741 and report back asap...

[spacecadet]

Originally Posted by Slugger

I need exception dumps. You need to enable SageTV logging and Jetty debug logging in order to log the exceptions. Without the exceptions all I know is that SRE stopped, but I have no idea why. I also need to know what build you're running. If you're not running the latest one available then please upgrade and try to reproduce the problem. (However, don't bother with 739, it needs some work done to it, which I'm doing right now.)

I've got the Sagetv log files and can provide those if you want them. I'm not sure how to turn on the Jetty debug logging. This was using build 737.

[Slugger]

http://forums.sagetv.com/forums/show...&postcount=185

The first paragraph explains how to enable the Jetty logging. In the meantime, move to 741 and let me know if you still the see the same problem.

[spacecadet]

Originally Posted by Slugger

http://forums.sagetv.com/forums/show...&postcount=185

The first paragraph explains how to enable the Jetty logging. In the meantime, move to 741 and let me know if you still the see the same problem.

It looks like there is some sort of startup issue with my server and the 2.4.0 versions of SRE. The application starts and I can access the Web UI, but no monitoring is occurring. This was my issue on Monday during the bowl game and I also seem to be having this problem with Build 741.

I'm trying to rollback to v2.3.1 without much luck, so right now the whole SRE app is hosed on my system. Logs are attached.

[Slugger]

The exception I'm seeing in your log is suggesting that it can't find the log4j jar file. It's definitely there (packaged in the war). What this could be is different versions of log4j conflicting with one another. SRE uses log4j-1.2.15. Another plugin might be using an older version. Is there a log4j-*.jar file in your SageTV/JARs folder? If so, that could be the cause, however don't delete them from the JARs folder since doing so will probably break whatever plugin(s) are using it. If there are log4j jars in your JARs folder then you can test the conflicting theory by removing the log4j jar from the sre.war file and then trying to restart Jetty/SRE. As a point of reference, I found log4j-1.2.15 and a log4j.jar in my JARs folder, yet have no trace of the errors your seeing in my SRE installation. All of my plugins package log4j in the war files and I've never run into this ClassNotFoundException you're seeing.

[Slugger]

A little more research is suggesting that this is a ClassLoader problem. Is there also a commons-logging.jar in your SageTV/JARs folder? If so, then I believe the problem is that in your env, for whatever reason, Jetty/SRE is loading the commons-logging jar from the JARs folder and the log4j jar from the SRE war (or vice versa) meaning the two can't see each other and so you get the ClassNotFoundException error. The easy fix (I believe), is to remove the commons-logging and log4j jars from the sre.war, but that can only be done if you have those jars in the JARs folder (b/c my code and 3rd party jars I use in my code rely on these libs). And if those jars are in the JARs folder then I guess I need to figure out if they're being provided by SageTV or if another plugin is including them. If they're being provided by SageTV and therefore we can assume they'll always be there then I can remove them from my war file and that should immediately fix your problem.

Anyone with a clean, plugin-free SageTV install able to confirm/deny if these jars are included by SageTV?

[cat6man]

hi slugger,
i'm not even trying the new version of SRE, since there's nothing to record until baseball season , but thought i'd throw a big thank you your way for keeping this going.................my vote for best sage customization.
happy new year

[voorhees]

Originally Posted by Slugger

Anyone with a clean, plugin-free SageTV install able to confirm/deny if these jars are included by SageTV?

@Slugger, I thought I had a clean version backed up, but upon inspection I did not. I did open up the SageTV WHS install file (SageTV_V6_6_2Setup-WHS.msi) and poked around. In the Cabs.w1.cab file I did find the commonslogging.jar file, but I did not find a copy of the log4j.jar file. I easily could be just missing it somewhere, but I only found one of the files in the SageTV install file.

[spacecadet]

Originally Posted by Slugger

A little more research is suggesting that this is a ClassLoader problem. Is there also a commons-logging.jar in your SageTV/JARs folder? If so, then I believe the problem is that in your env, for whatever reason, Jetty/SRE is loading the commons-logging jar from the JARs folder and the log4j jar from the SRE war (or vice versa) meaning the two can't see each other and so you get the ClassNotFoundException error. The easy fix (I believe), is to remove the commons-logging and log4j jars from the sre.war, but that can only be done if you have those jars in the JARs folder (b/c my code and 3rd party jars I use in my code rely on these libs). And if those jars are in the JARs folder then I guess I need to figure out if they're being provided by SageTV or if another plugin is including them. If they're being provided by SageTV and therefore we can assume they'll always be there then I can remove them from my war file and that should immediately fix your problem.

Anyone with a clean, plugin-free SageTV install able to confirm/deny if these jars are included by SageTV?

I do have the commons-logging.jar in my JARs folder (no log4j, though). I'll do some poking around this weekend to see if I can figure out which plugin is requiring it.

[spacecadet]

Originally Posted by spacecadet

I do have the commons-logging.jar in my JARs folder (no log4j, though). I'll do some poking around this weekend to see if I can figure out which plugin is requiring it.

I confirmed that core Sage TV (not a plugin) uses commons-logging. Although Sage TV is packaging commons-logging 1.0 and SRE is using 1.1, so I am hesitant to overwrite what is in the JARs directory.

Interestingly, I was able to get SRE 2.3.1 working again last night. SRE 2.3.1 also packages commons-logging and log4j, so I am not sure what is different about 2.4.0 that was start causing a problem. I may try to redeploy 2.4.0 today and see what happens.

[Slugger]

On my system I have log4j and commons-logging in my JARs folder. So some other plugin is providing log4j, but it's probably enough to ensure that both jars are being pulled from the same spot, which is why I'm not seeing the ClassLoader problem. We now know that SageTV provides commons-logging and not log4j so the solution here is to remove commons-logging and log4j from the sre.war and copy the log4j into JARs. Upgrading commons-logging to 1.1 shouldn't break anything (though I'd keep a backup of the original somewhere, just in case). I'll repackage SRE now and see if that helps.

[Slugger]

Ok, follow this wiki doc to upgrade SageTV's commons-logging package then upgrade to SRE snapshot 743. I've done it all and everything still seems to be working as expected. Please report back.

Apparently, simply upgrading SageTV's commons-logging to 1.1.1 should be enough to fix the problem as the release notes from 1.0 to 1.1.x describe this exact scenario with ClassLoader problems that is apparently fixed in 1.1. So SageTV should really upgrade its commons-logging jar itself (perhaps I'll send a bug report along). Anyway, please give it a shot and let me know if you're able to load SRE.

[spacecadet]

Originally Posted by Slugger

Ok, follow this wiki doc to upgrade SageTV's commons-logging package then upgrade to SRE snapshot 743. I've done it all and everything still seems to be working as expected. Please report back.

Apparently, simply upgrading SageTV's commons-logging to 1.1.1 should be enough to fix the problem as the release notes from 1.0 to 1.1.x describe this exact scenario with ClassLoader problems that is apparently fixed in 1.1. So SageTV should really upgrade its commons-logging jar itself (perhaps I'll send a bug report along). Anyway, please give it a shot and let me know if you're able to load SRE.

Ok. That seemed to work. SRE appears to be monitoring again... although the About page thinks I am running 2.4.0.741 (not 743). The timestamp on the war file matches that of 743, so I think I have the correct version installed... at any rate, it is working now.

Thanks!

[Slugger]

Originally Posted by spacecadet

Ok. That seemed to work. SRE appears to be monitoring again... although the About page thinks I am running 2.4.0.741 (not 743). The timestamp on the war file matches that of 743, so I think I have the correct version installed... at any rate, it is working now.

Thanks!

Clear your browser cache... sometimes the GUI gets cached by your browser. In this case it shouldn't hurt anything since I made no GUI changes, but clearing your cache should ensure that the latest GUI is loaded.

[spacecadet]

Originally Posted by Slugger

Clear your browser cache... sometimes the GUI gets cached by your browser. In this case it shouldn't hurt anything since I made no GUI changes, but clearing your cache should ensure that the latest GUI is loaded.

Cleared cache and now the GUI is reporting the correct version. Thanks!