[jboss-jira] [JBoss JIRA] (AS7-4321) OSGi management console needs inspector of wiring

Thomas Diesler (JIRA) jira-events at lists.jboss.org
Thu Mar 29 02:32:47 EDT 2012


     [ https://issues.jboss.org/browse/AS7-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler moved JBOSGI-539 to AS7-4321:
--------------------------------------------

              Project: Application Server 7  (was: JBoss OSGi)
                  Key: AS7-4321  (was: JBOSGI-539)
             Workflow: GIT Pull Request workflow   (was: jira)
    Affects Version/s: 7.1.1.Final
                           (was: JBossOSGi 1.0.0)
          Component/s: OSGi
                           (was: Core Framework)
             Security:     (was: Public)

    
> OSGi management console needs inspector of wiring
> -------------------------------------------------
>
>                 Key: AS7-4321
>                 URL: https://issues.jboss.org/browse/AS7-4321
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: OSGi
>    Affects Versions: 7.1.1.Final
>         Environment: Mac OS X 10.7.3
>            Reporter: Tim Diekmann
>            Assignee: Thomas Diesler
>
> The OSGi management console for AS 7 needs a viewer of the current wiring. The console log showed the following error on start of the bundle and there is no way to inspect the wiring to see where the problem lies and how to solve it. There is some inconsistency in the deployment, but how to find out what?
> 00:09:14,480 ERROR [org.mortbay.log] (HttpManagementService-threads - 3) Error starting handlers: java.lang.IncompatibleClassChangeError: Class org.eclipse.equinox.http.servlet.HttpServiceServlet does not implement the requested interface javax.servlet.Servlet
> 	at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.init(HttpServerManager.java:294)
> 	at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431)
> 	at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
> 	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> 	at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:681)
> 	at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
> 	at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
> 	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> 	at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> 	at org.mortbay.jetty.Server.doStart(Server.java:224)
> 	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> 	at org.eclipse.equinox.http.jetty.internal.HttpServerManager.updated(HttpServerManager.java:109)
> 	at org.eclipse.equinox.http.jetty.internal.Activator.start(Activator.java:60)
> 	at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:300)
> 	at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223)
> 	at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:488)
> 	at org.jboss.as.osgi.parser.BundleRuntimeHandler.handleOperation(BundleRuntimeHandler.java:132)
> 	at org.jboss.as.osgi.parser.BundleRuntimeHandler.executeRuntimeStep(BundleRuntimeHandler.java:89)
> 	at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90)
> 	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387)
> 	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274)
> 	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202)
> 	at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:461)
> 	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387)
> 	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274)
> 	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202)
> 	at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121)
> 	at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:304)
> 	at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:294)
> 	at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:294)
> 	at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:201)
> 	at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:208)
> 	at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51)
> 	at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
> 	at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69)
> 	at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
> 	at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710)
> 	at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
> 	at org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:54)
> 	at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
> 	at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
> 	at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list