[jboss-osgi-issues] [JBoss JIRA] Updated: (JBOSGI-386) Invoking Refresh Packages on the framework from Web Console causes issues

Invoking Refresh Packages on the framework from Web Console causes issues ------------------------------------------------------------------------- Key: JBOSGI-386 URL: https://jira.jboss.org/browse/JBOSGI-386 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public(Everyone can see) Components: jboss-osgi-jmx, jboss-osgi-webconsole Affects Versions: JBossOSGi 1.0.0 Beta8 Reporter: David Bosschaert Assignee: David Bosschaert Fix For: JBossOSGi 1.0.0 Beta9 Refreshing individual bundles from the web console works fine, but when invoking 'Refresh Packages' on the whole framework, a number of bundles cause issues. The first issue appears when we're trying to refresh EventAdmin: java.lang.IllegalStateException: Cannot remove [jbosgi."org.apache.felix.eventadmin".ManagedService.40] from: [jbosgi.jboss-osgi-http.ManagedService.14, jbosgi.jboss-osgi-webconsole.ManagedService.22] at org.jboss.osgi.container.plugin.internal.ServiceManagerPluginImpl.unregisterNameAssociation(ServiceManagerPluginImpl.java:393) at org.jboss.osgi.container.plugin.internal.ServiceManagerPluginImpl.unregisterService(ServiceManagerPluginImpl.java:428) at org.jboss.osgi.container.bundle.ServiceState.unregister(ServiceState.java:228) at org.jboss.osgi.container.bundle.HostBundle.stopInternal(HostBundle.java:304) at org.jboss.osgi.container.bundle.AbstractBundle.stop(AbstractBundle.java:494) at org.jboss.osgi.container.bundle.HostBundle.stop(HostBundle.java:249) at org.jboss.osgi.container.plugin.internal.PackageAdminPluginImpl$1.run(PackageAdminPluginImpl.java:279) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Which is then followed by an issue around the JMXConnectorServer: [JMXConnectorService] Cannot stop JMXConnectorServer java.io.IOException: Cannot bind to URL: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:804) at javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.java:555) at org.jboss.osgi.jmx.internal.JMXConnectorService.stop(JMXConnectorService.java:90) at org.jboss.osgi.jmx.internal.JMXServiceActivator.stop(JMXServiceActivator.java:133) at org.jboss.osgi.container.bundle.HostBundle.stopInternal(HostBundle.java:292) at org.jboss.osgi.container.bundle.AbstractBundle.stop(AbstractBundle.java:494) at org.jboss.osgi.container.bundle.HostBundle.stop(HostBundle.java:249) at org.jboss.osgi.container.plugin.internal.PackageAdminPluginImpl$1.run(PackageAdminPluginImpl.java:279) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325) at javax.naming.InitialContext.unbind(InitialContext.java:416) at javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.java:547) ... 9 more Needless to say is that restarting these also causes issues since they weren't properly shut down.