Skip to main content

HN without DVR configuration in Rel-C

2 replies [Last post]
Joined: 2010-10-13

I currently use the HN without DVR configuration supported in Rel-C version.
There is no issue to build this configuration but, when I boot up the stack, it generated some waring message with regards to load "org.cablelabs.impl.manager.RecordingManager" class.

[RI.Stack][DEBUG] 11127 [main] DEBUG ManagerManager - iniz: Recording,org.cablelabs.impl.manager.RecordingManager
[RI.Stack][WARN] 11132 [main] WARN ManagerManager - Could not load Manager class: org.cablelabs.impl.manager.RecordingManager
[RI.Stack][WARN] java.lang.ClassNotFoundException: org.cablelabs.impl.manager.RecordingManager
at sun.misc.Launcher$AppClassLoader.findClass(
at java.lang.ClassLoader.loadClass(
at sun.misc.Launcher$AppClassLoader.loadClass(
at java.lang.ClassLoader.loadClass(
at java.lang.ClassLoader.loadClassInternal(
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(
at org.cablelabs.impl.manager.ManagerManager.staticIniz(
at org.cablelabs.impl.manager.ManagerManager.(
at java.lang.Class.runStaticInitializers(
at org.cablelabs.impl.ocap.TimeZoneInitializer.initTimeZone(
at org.cablelabs.impl.ocap.OcapMain.initJava(
at org.cablelabs.impl.ocap.OcapMain.main(

After looking over the and the, I found that the definitions of "OCAP.mgrmgr.manager.Recording" are duplicated so that the ManagerManager tried to load this DVR-releated Manager according to the file.

Is it a bug ?

Also, I found that there is no definition for "HNAPIManager" in the even though the exists under RI_Stack/java/src/hn directory.

Does this manager need to be load at boot time ?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2009-07-05

As to the first question: technically, it is a bug, but a minor one. It is benign--the only symptom is the occurrence of the stack trace in the log.

As to the second question: no.

Joined: 2004-08-13

Have you, or are you planning to address this issue? Wouldn't a work around for now be to remove the value from the file?

Is there any plan to make the file be generated dynamically based on the properties set in the file in order to address this? Would that be address this properly? I'm considering doing some modifications along these lines and I wanted to find out what CableLabs might be thinking here.