You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/02/03 13:23:28 UTC
[jira] Created: (FELIX-2034) WebConsole fails to register if Http
Service is registered after Web Console start
WebConsole fails to register if Http Service is registered after Web Console start
----------------------------------------------------------------------------------
Key: FELIX-2034
URL: https://issues.apache.org/jira/browse/FELIX-2034
Project: Felix
Issue Type: Bug
Components: Web Console
Affects Versions: webconsole-2.0.6
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: webconsole-3.0.0
With fixing FELIX- 2009 the field webManagerRoot is only assigned if the OsgiManager is bound to the Http Service. If the OsgiManager starts and is configured before the Http Service is registered, the field remains unset and registration of the Http Service may cause the following dump:
03.02.2010 09:16:47.216 *ERROR* [FelixStartLevel]
org.apache.felix.webconsole bindHttpService: Problem setting up
(org.ops4j.lang.NullArgumentException: Alias is null.)
org.ops4j.lang.NullArgumentException: Alias is null.
at org.ops4j.lang.NullArgumentException.validateNotNull(NullArgumentException.java:75)
at org.ops4j.pax.web.service.internal.model.ServletModel.validateAlias(ServletModel.java:120)
at org.ops4j.pax.web.service.internal.model.ServletModel.<init>(ServletModel.java:44)
at org.ops4j.pax.web.service.internal.HttpServiceStarted.registerServlet(HttpServiceStarted.java:128)
at org.ops4j.pax.web.service.internal.HttpServiceProxy.registerServlet(HttpServiceProxy.java:53)
at org.apache.felix.webconsole.internal.servlet.OsgiManager.bindHttpService(OsgiManager.java:689)
at org.apache.felix.webconsole.internal.servlet.OsgiManager$HttpServiceTracker.addingService(OsgiManager.java:498)
at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1030)
at org.osgi.util.tracker.ServiceTracker$Tracked.track(ServiceTracker.java:1008)
The only resolution here is to restart the WebConsole bundle or reconfigure the Web Console for the registration to take place again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2034) WebConsole fails to register if Http
Service is registered after Web Console start
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed FELIX-2034.
-----------------------------------
> WebConsole fails to register if Http Service is registered after Web Console start
> ----------------------------------------------------------------------------------
>
> Key: FELIX-2034
> URL: https://issues.apache.org/jira/browse/FELIX-2034
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-2.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: webconsole-3.0.0
>
>
> With fixing FELIX- 2009 the field webManagerRoot is only assigned if the OsgiManager is bound to the Http Service. If the OsgiManager starts and is configured before the Http Service is registered, the field remains unset and registration of the Http Service may cause the following dump:
> 03.02.2010 09:16:47.216 *ERROR* [FelixStartLevel]
> org.apache.felix.webconsole bindHttpService: Problem setting up
> (org.ops4j.lang.NullArgumentException: Alias is null.)
> org.ops4j.lang.NullArgumentException: Alias is null.
> at org.ops4j.lang.NullArgumentException.validateNotNull(NullArgumentException.java:75)
> at org.ops4j.pax.web.service.internal.model.ServletModel.validateAlias(ServletModel.java:120)
> at org.ops4j.pax.web.service.internal.model.ServletModel.<init>(ServletModel.java:44)
> at org.ops4j.pax.web.service.internal.HttpServiceStarted.registerServlet(HttpServiceStarted.java:128)
> at org.ops4j.pax.web.service.internal.HttpServiceProxy.registerServlet(HttpServiceProxy.java:53)
> at org.apache.felix.webconsole.internal.servlet.OsgiManager.bindHttpService(OsgiManager.java:689)
> at org.apache.felix.webconsole.internal.servlet.OsgiManager$HttpServiceTracker.addingService(OsgiManager.java:498)
> at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1030)
> at org.osgi.util.tracker.ServiceTracker$Tracked.track(ServiceTracker.java:1008)
> The only resolution here is to restart the WebConsole bundle or reconfigure the Web Console for the registration to take place again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2034) WebConsole fails to register if Http
Service is registered after Web Console start
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved FELIX-2034.
--------------------------------------
Resolution: Fixed
Fixed in Rev. 906031
> WebConsole fails to register if Http Service is registered after Web Console start
> ----------------------------------------------------------------------------------
>
> Key: FELIX-2034
> URL: https://issues.apache.org/jira/browse/FELIX-2034
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-2.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: webconsole-3.0.0
>
>
> With fixing FELIX- 2009 the field webManagerRoot is only assigned if the OsgiManager is bound to the Http Service. If the OsgiManager starts and is configured before the Http Service is registered, the field remains unset and registration of the Http Service may cause the following dump:
> 03.02.2010 09:16:47.216 *ERROR* [FelixStartLevel]
> org.apache.felix.webconsole bindHttpService: Problem setting up
> (org.ops4j.lang.NullArgumentException: Alias is null.)
> org.ops4j.lang.NullArgumentException: Alias is null.
> at org.ops4j.lang.NullArgumentException.validateNotNull(NullArgumentException.java:75)
> at org.ops4j.pax.web.service.internal.model.ServletModel.validateAlias(ServletModel.java:120)
> at org.ops4j.pax.web.service.internal.model.ServletModel.<init>(ServletModel.java:44)
> at org.ops4j.pax.web.service.internal.HttpServiceStarted.registerServlet(HttpServiceStarted.java:128)
> at org.ops4j.pax.web.service.internal.HttpServiceProxy.registerServlet(HttpServiceProxy.java:53)
> at org.apache.felix.webconsole.internal.servlet.OsgiManager.bindHttpService(OsgiManager.java:689)
> at org.apache.felix.webconsole.internal.servlet.OsgiManager$HttpServiceTracker.addingService(OsgiManager.java:498)
> at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1030)
> at org.osgi.util.tracker.ServiceTracker$Tracked.track(ServiceTracker.java:1008)
> The only resolution here is to restart the WebConsole bundle or reconfigure the Web Console for the registration to take place again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.