Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
webconsole-1.2.2
-
None
-
org.eclipse.osgi_3.4.2.R34x_v20080826-1230
org.eclipse.equinox.cm_1.0.0.v20080509-1800
org.ops4j.pax.web.service_0.5.1
org.apache.felix.webconsole_1.2.2
Description
ERROR root - ResourceModel{id=org.ops4j.pax.web.service.internal.model.ResourceModel-3,urlPatterns=[/system/console/res/*],alias=/system/console/res,servlet=org.ops4j.pax.web.service.internal.ResourceServlet@1bcb7c74,initParams={},context=ContextModel{,id=org.ops4j.pax.web.service.internal.model.ContextModel-1,name=,httpContext=org.apache.felix.webconsole.internal.servlet.OsgiManagerHttpContext@1d489e0e,contextParams={}}} was not found
java.lang.IllegalStateException: ResourceModel{id=org.ops4j.pax.web.service.internal.model.ResourceModel-3,urlPatterns=[/system/console/res/*],alias=/system/console/res,servlet=org.ops4j.pax.web.service.internal.ResourceServlet@1bcb7c74,initParams={},context=ContextModel{,id=org.ops4j.pax.web.service.internal.model.ContextModel-1,name=,httpContext=org.apache.felix.webconsole.internal.servlet.OsgiManagerHttpContext@1d489e0e,contextParams={}}} was not found
at org.ops4j.pax.web.service.internal.JettyServerImpl.removeServlet(JettyServerImpl.java:217)
at org.ops4j.pax.web.service.internal.ServerControllerImpl$Started.removeServlet(ServerControllerImpl.java:219)
at org.ops4j.pax.web.service.internal.ServerControllerImpl.removeServlet(ServerControllerImpl.java:95)
at org.ops4j.pax.web.service.internal.HttpServiceStarted.unregister(HttpServiceStarted.java:230)
at org.ops4j.pax.web.service.internal.HttpServiceProxy.unregister(HttpServiceProxy.java:69)
at org.apache.felix.webconsole.internal.servlet.OsgiManager.unbindHttpService(OsgiManager.java:594)
at org.apache.felix.webconsole.internal.servlet.OsgiManager.updateConfiguration(OsgiManager.java:720)
at org.apache.felix.webconsole.internal.servlet.ConfigurationListener.updated(ConfigurationListener.java:57)
Thrown on a clean startup; subsequently the webconsole is completely broken.
Probably the environment plays a role in this issue, nonetheless, the OsgiManager should probably never try to unregister something it didn't register in first place.