Skip to main content

IllegalArgumentException observed while creating MediaServer

3 replies [Last post]
srinivasrk
Offline
Joined: 2011-10-31
Points: 0

We had observed IllegalArgumentException while RI (RI 1.2.1 REL A.1) is trying to create MediaServer on Linux environment. But now we are not able to reproduce this issue on the same version of RI. It can be a platform dependent issue. Can anyone please look at the below exception stack trace and let us know whether we can ignore this issue or not?

20120123 13:38:02.234 WARN RI.Stack- 2858 [main] WARN upnp.MediaServer - Unable to create MediaServer
20120123 13:38:02.237 WARN RI.Stack- java.lang.IllegalArgumentException: Invalid device description org.cybergarage.upnp.device.InvalidDescriptionException: org.cybergarage.xml.ParserException: java.lang.NullPointerException
20120123 13:38:02.238 WARN RI.Stack- at org.cablelabs.impl.ocap.hn.upnp.server.UPnPManagedDeviceImpl.reloadDevice(UPnPManagedDeviceImpl.java:637)
20120123 13:38:02.238 WARN RI.Stack- at org.cablelabs.impl.ocap.hn.upnp.server.UPnPManagedDeviceImpl.addIcon(UPnPManagedDeviceImpl.java:458)
20120123 13:38:02.238 WARN RI.Stack- at org.cablelabs.impl.ocap.hn.upnp.server.UPnPDeviceManagerImpl.createDevice(UPnPDeviceManagerImpl.java:207)
20120123 13:38:02.238 WARN RI.Stack- at org.cablelabs.impl.ocap.hn.upnp.MediaServer.<init>(MediaServer.java:131)
20120123 13:38:02.238 WARN RI.Stack- at org.cablelabs.impl.ocap.hn.upnp.MediaServer.<clinit>(MediaServer.java:87)
20120123 13:38:02.238 WARN RI.Stack- at java.lang.Class.runStaticInitializers(Class.java:1643)
20120123 13:38:02.238 WARN RI.Stack- at org.cablelabs.impl.ocap.hn.NetManagerImpl.<init>(NetManagerImpl.java:116)
20120123 13:38:02.238 WARN RI.Stack- at org.cablelabs.impl.ocap.hn.NetManagerImpl.instance(NetManagerImpl.java:205)
20120123 13:38:02.238 WARN RI.Stack- at org.ocap.hn.NetManager.getInstance(NetManager.java:74)
20120123 13:38:02.238 WARN RI.Stack- at org.cablelabs.impl.manager.ManagerInfo.getInstanceImpl(ManagerManager.java:758)
20120123 13:38:02.239 WARN RI.Stack- at org.cablelabs.impl.manager.ManagerInfo.getInstance(ManagerManager.java:667)
20120123 13:38:02.239 WARN RI.Stack- at org.cablelabs.impl.manager.ManagerManager.getInstance(ManagerManager.java:216)
20120123 13:38:02.239 WARN RI.Stack- at org.cablelabs.impl.manager.ManagerManager.startAll(ManagerManager.java:123)
20120123 13:38:02.239 WARN RI.Stack- at org.cablelabs.impl.ocap.OcapMain.startManagers(OcapMain.java:287)
20120123 13:38:02.239 WARN RI.Stack- at org.cablelabs.impl.ocap.OcapMain.main(OcapMain.java:105)

Reply viewing options

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

This issue should not be ignored. Please file an Issue Tracker issue (including a complete debug log if you have one).

Looking at the stack trace provided and your description which implies it is an intermitent issue/not easily reproducible, I believe this may be classified as a "brownian motion" issue. A "brownian motion" issue is a random intermittent failure which has been observed during testing. In many cases, the failure is "local device not found". The stack trace above would definately result in "local device not found".

The Cablelabs RI team has a page on the public Wiki describing the current efforts to address this "brownian motion:

https://community.cablelabs.com/wiki/display/OCORI/RI_Stack+Stability-Robustness


ssathish
Offline
Joined: 2011-05-26
Points: 0

CL issue tracker# OCAP_RI-617

dgalliga
Offline
Joined: 2009-07-25
Points: 0

A fix to JSR280 has been applied to the trunk at r32447, it appears to resolve the issue.
OCAP_RI-617 has been updated to reflect the current status.