Skip to main content

Permission Exception when Device Extension is enabled in 1.1.4

8 replies [Last post]
amirn
Offline
Joined: 2009-05-06

We are getting the following exception when we enable Device Settings Extension.
What specific permission is require for this to work?

Thanks.

(JVM stdout) org.havi.ui.HPermissionDeniedException: Device is not reserved
(JVM stdout) at org.havi.ui.HScreenDevice.withReservation(Unknown Source)
(JVM stdout) at org.havi.ui.HScreenDevice.withReservation(Unknown Source)
(JVM stdout) at org.cablelabs.impl.havi.port.mpe.HDVideoDevice.withReservation(Unknown Source)
(JVM stdout) at org.cablelabs.impl.havi.port.mpe.HDCoherentConfig.select(Unknown Source)
(JVM stdout) at org.cablelabs.impl.havi.port.mpe.HDScreen.selectCoherentConfig(Unknown Source)
(JVM stdout) at org.cablelabs.impl.havi.port.mpe.HDScreen.setCoherentConfigurationWithAspectRatio(Unknown Source)
(JVM stdout) at org.cablelabs.impl.ocap.hardware.device.HostSettingsProxy.updateHScreenAspectRatio(Unknown Source)
(JVM stdout) at org.cablelabs.impl.ocap.hardware.device.HostSettingsProxy.setMainVideoOutputPortNoPerm(Unknown Source)
(JVM stdout) at org.cablelabs.impl.ocap.hardware.device.HostSettingsProxy.initFromPersistence(Unknown Source)
(JVM stdout) at org.cablelabs.impl.ocap.hardware.device.DeviceSettingsHostPersistence.initHostSettings(Unknown Source)
(JVM stdout) at org.cablelabs.impl.ocap.hardware.device.HostSettingsProxy.(Unknown Source)
(JVM stdout) at org.cablelabs.impl.ocap.hardware.device.DeviceSettingsHostImpl.(Unknown Source)
(JVM stdout) at org.cablelabs.impl.manager.host.DeviceSettingsHostManagerImpl.getHostInstance(Unknown Source)
(JVM stdout) at org.ocap.hardware.Host.getInstance(Unknown Source)
(JVM stdout) at org.cablelabs.impl.ocap.manager.eas.EASManagerImpl.(Unknown Source)
(JVM stdout) at org.cablelabs.impl.ocap.manager.eas.DavicEASManager.(Unknown Source)
(JVM stdout) at org.cablelabs.impl.ocap.manager.eas.DavicEASManager.getInstance(Unknown Source)
(JVM stdout) at org.cablelabs.impl.manager.ManagerInfo.getInstanceImpl(Unknown Source)
(JVM stdout) at org.cablelabs.impl.manager.ManagerInfo.getInstance(Unknown Source)
(JVM stdout) at org.cablelabs.impl.manager.ManagerManager.getInstance(Unknown Source)
(JVM stdout) at org.cablelabs.impl.manager.ManagerManager.startAll(Unknown Source)
(JVM stdout) at org.cablelabs.impl.ocap.OcapMain.startManagers(Unknown Source)
(JVM stdout) at org.cablelabs.impl.ocap.OcapMain.main(Unknown Source)
###################

Reply viewing options

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

Greg,

This turned out to be an RI bug with the device reservation mechanism. A patch was provided to me and it was also submitted to the svn repository.
See https://ocap-ri.dev.java.net/issues/show_bug.cgi?id=211

arorholt
Offline
Joined: 2010-04-29

In /ri/RI_Stack/java/src/base/org/cablelabs/impl/havi/package.html there is the following reference:
For additional information, please see:
* CableLabs HAVi Porting Guide
I have been unable to locate this file. Is this still in existence and valid? If so, where can we get it?

arorholt
Offline
Joined: 2010-04-29

The last ended in the wrong place. It was meant to go to MPEOS Disp clarifications issue.

amirn
Offline
Joined: 2009-05-06

It looks like this is an internal call from the EAS manager trying to get an instance of org.ocap.hardware.Host.

Host should be independent of whether DS is enabled or not. In this case it looks like there is an implementation dependency that requires the HScreen Device to be reserved by the caller.

Please comment,
Thanks.

greg80303
Offline
Joined: 2008-07-03

We have several implementations of the Host class as defined in OCAP. When you have enabled the Device Settings extension in your build, the stack instantiates an instance of DeviceSettingsHostManagerImpl. When Device Settings extension is not enabled, this class is never instantiated (nor is it compiled into the OCAP jar file). Instead, the stack instantiates HostManagerImpl.

I will look more into this permission issue. We run with DS enabled all the time and we have not seen this on the PC platform.

Can you tell me about your complete configuration as far as extensions? Which extensions are enabled and disabled? Perhaps there is a combination that we have not tested that is causing the problem.

G

Message was edited by: greg80303

alancohn
Offline
Joined: 2009-09-29

I have the problem of running EAS without DS and host apps.
The host app (AppLauncher) starts up but nothing appears on the screen.
I've placed log messages in AppLauncher and it runs without any exceptions however nothing appears on the screen.
When I disable EAS from running then the AppLauncher's display is visible on the screen.
Please comment.

amirn
Offline
Joined: 2009-05-06

This maybe a different issue.In my case the problem was always when DS was enabled.
Do you see any java exceptions in your log? Was there any EAS message being broadcast?

If this is on the RI Emulator, try pressing the Power Button.

alancohn
Offline
Joined: 2009-09-29

No java exceptions logged in EAS nor AppLauncher.
No EAS message being broadcast.
On actual hardware (not emulator).