Skip to main content

RI doesn't automatically resume a recording request created via ServiceContextRecordingSpec

2 replies [Last post]
prasobk
Offline
Joined: 2011-01-05
Points: 0

1. Create a recording request using a ServiceContextRecordingSpec.
2. Reboot the box before the end time of the recording request is reached
Here we can see that the recording will not automatically resume. If we analyze the logs we can see that RI actually tries to restore the recording but fails due to a NullPointerException
java.lang.NullPointerException
at org.cablelabs.impl.manager.recording.RecordingImpl.initiateRecordingProcess(RecordingImpl.java:1542)
at org.cablelabs.impl.manager.recording.RecordingImpl$IStatePending.handleStart(RecordingImpl.java:4248)
at org.cablelabs.impl.manager.recording.RecordingImpl.startInternal(RecordingImpl.java:3019)
at org.cablelabs.impl.manager.recording.Scheduler.timerWentOff(Scheduler.java:629)
at javax.tv.util.TVTimerSpec.notifyListeners(TVTimerSpec.java:304)
at org.cablelabs.impl.manager.timer.TimerMgrJava2$TVTimerImpl$1.run(TimerMgrJava2.java:434)
at java.util.TimerThread.mainLoop(Timer.java:498)
at java.util.TimerThread.run(Timer.java:428)
at java.lang.Thread.startup(Thread.java:785)

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
cpratt
Offline
Joined: 2008-12-18
Points: 0

ServiceContextRecordingSpecs are constrained in time by the serviceContext.select().
From Section 6.2.1.1.3 of the DVR I06 specification:

  • Recordings initiated with the invocation of the record method with a ServiceContextRecordingSpec as the parameter SHALL be terminated if the service context is destroyed, or if an application selects another service on the service context.

A reboot destroys all ServiceContext and, therefore, no SCRS-based recordings are resumed on reboot.

dhooley
Offline
Joined: 2008-04-23
Points: 0

Please open a defect in the Issue Navigator database for this problem. Be sure to describe the version of the RI you are running against, and attach a log file.