We've been trying out Skifta, our mobile app, which uses felix (v3.2.2) on the latest version of Android (v4.0 - Ice Cream Sandwich) and have found an issue when trying to start the jetty bundle (v2.2.0). We need some help to solve this problem given that Android v4.0 will be officially released soon.
Below is the stack trace: 11-09 12:03:36.507: E/SkiftaService(2979): unable to load and start bundle from org.apache.felix.http.jetty-2.2.0.jar 11-09 12:03:36.507: E/SkiftaService(2979): org.osgi.framework.BundleException: Activator start error in bundle org.apache.felix.http.jetty [3]. 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.framework.Felix.activateBundle(Felix.java:1951) 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.framework.Felix.startBundle(Felix.java:1822) 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:927) 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:914) 11-09 12:03:36.507: E/SkiftaService(2979): at com.skifta.android.client.SkiftaService.startOSGi(SkiftaService.java:1208) 11-09 12:03:36.507: E/SkiftaService(2979): at com.skifta.android.client.SkiftaService.init(SkiftaService.java:675) 11-09 12:03:36.507: E/SkiftaService(2979): at com.skifta.android.client.SkiftaService$1.run(SkiftaService.java:384) 11-09 12:03:36.507: E/SkiftaService(2979): at java.lang.Thread.run(Thread.java:856) 11-09 12:03:36.507: E/SkiftaService(2979): Caused by: java.lang.ExceptionInInitializerError 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.http.base.internal.AbstractHttpActivator.doStart(AbstractH ttpActivator.java:45) 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.http.jetty.internal.JettyActivator.doStart(JettyActivator. java:29) 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.http.base.internal.AbstractActivator.start(AbstractActivat or.java:41) 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.ja va:629) 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.framework.Felix.activateBundle(Felix.java:1904) 11-09 12:03:36.507: E/SkiftaService(2979): ... 7 more 11-09 12:03:36.507: E/SkiftaService(2979): Caused by: java.lang.NullPointerException 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.framework.ModuleImpl.doImplicitBootDelegation(ModuleImpl.j ava:1531) 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.framework.ModuleImpl.searchDynamicImports(ModuleImpl.java: 1508) 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(Modul eImpl.java:759) 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.framework.ModuleImpl.getResourceByDelegation(ModuleImpl.ja va:677) 11-09 12:03:36.507: E/SkiftaService(2979): at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.getResource(ModuleI mpl.java:2061) 11-09 12:03:36.507: E/SkiftaService(2979): at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:434) 11-09 12:03:36.507: E/SkiftaService(2979): at java.util.ResourceBundle.handleGetBundle(ResourceBundle.java:514) 11-09 12:03:36.507: E/SkiftaService(2979): at java.util.ResourceBundle.getBundle(ResourceBundle.java:227) 11-09 12:03:36.507: E/SkiftaService(2979): at java.util.ResourceBundle.getBundle(ResourceBundle.java:140) 11-09 12:03:36.507: E/SkiftaService(2979): at javax.servlet.GenericServlet.<clinit>(GenericServlet.java:64) 11-09 12:03:36.507: E/SkiftaService(2979): ... 12 more We've been able to identify that the root cause of the problem is that SecurityManagerEx.getClassContext() is returning null. Looking at the framework code it doesn't look like it would ever expect to get back null, so we're not sure if this is a bug in felix or Android v4.0 is doing something unexpected. Points to note: - This only occurs on Android v4.0 and doesn't happen on previous versions of Android which work fine. - We've only seen this happen with the jetty bundle: it doesn't seem to be a problem for every bundle or at least the bundles we use. - We've tried different versions of the framework including the latest with the same result, so it isn't related to the framework version we're using. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
