You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Ian Boston (JIRA)" <ji...@apache.org> on 2009/05/08 19:38:51 UTC
[jira] Updated: (FELIX-1135) NPE When accessing the configuration
view in webconsole with Felix as the container (seen in the Sling 5
release)
[ https://issues.apache.org/jira/browse/FELIX-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated FELIX-1135:
------------------------------
Priority: Critical (was: Major)
This is probably critical, and for anyone who wants to configure anything in the web console using felix as the framework, its probably a blocker.
> NPE When accessing the configuration view in webconsole with Felix as the container (seen in the Sling 5 release)
> -----------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-1135
> URL: https://issues.apache.org/jira/browse/FELIX-1135
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-1.2.8
> Reporter: Ian Boston
> Priority: Critical
>
> Accesing the webconsole in the sling-5-release using felix 1.6.1 with 1.2.8 of the web console gives the following error.
> HTTP ERROR 500
> Problem accessing /system/console/configMgr. Reason:
> Filter cannot be null
> Caused by:
> java.lang.NullPointerException: Filter cannot be null
> at org.apache.felix.framework.FilterImpl.(FilterImpl.java:59)
> at org.apache.felix.framework.BundleContextImpl.createFilter(BundleContextImpl.java:102)
> at org.apache.felix.webconsole.internal.compendium.ConfigManager.renderContent(ConfigManager.java:228)
> at org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:113)
> at org.apache.felix.webconsole.internal.compendium.ConfigManager.doGet(ConfigManager.java:201)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:311)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
> at org.ops4j.pax.web.service.internal.HttpServiceServletHandler.handle(HttpServiceServletHandler.java:64)
> at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
> at org.ops4j.pax.web.service.internal.HttpServiceContext.handle(HttpServiceContext.java:111)
> at org.ops4j.pax.web.service.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:64)
> at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:324)
> at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535)
> at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:865)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
> at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.