[jboss-osgi-issues] [JBoss JIRA] Commented: (JBOSGI-464) Felix web console does not appear any more on http://localhost:8090/jboss-osgi

David Bosschaert (JIRA) jira-events at lists.jboss.org
Fri Jun 17 04:37:23 EDT 2011


    [ https://issues.jboss.org/browse/JBOSGI-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609381#comment-12609381 ] 

David Bosschaert commented on JBOSGI-464:
-----------------------------------------

This can be fixed by changing the ordering in which the bundles are started. This surprises me a bit because the order shouldn't matter, but at least it's a workaround... Created JBOSGI-466 for this.

For AS 7.0.0 I'll change the start order to work around this.

> Felix web console does not appear any more on http://localhost:8090/jboss-osgi
> ------------------------------------------------------------------------------
>
>                 Key: JBOSGI-464
>                 URL: https://issues.jboss.org/browse/JBOSGI-464
>             Project: JBoss OSGi
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jboss-osgi-webconsole
>    Affects Versions: JBossOSGi 1.0.0 Beta10
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>
> When increasing the start level in AS7 to 3, the web console bundle is being started, however it's not accessible from http://localhost:8090/jboss-osgi
> 12:19:33,190 INFO  [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-15) Bundle started: org.apache.felix.webconsole:3.1.6.SP1
> 12:19:33,218 INFO  [org.apache.aries.jmx] (Thread-28) Registering MBean with ObjectName [osgi.compendium:service=cm,version=1.3] for service with service.id [23]
> 12:19:33,221 INFO  [org.apache.aries.jmx] (Thread-28) Registering org.osgi.jmx.service.cm.ConfigurationAdminMBean to MBeanServer org.jboss.as.jmx.tcl.TcclMBeanServer at 556292a4 with name osgi.compendium:service=cm,version=1.3
> 12:19:33,226 INFO  [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-15) Bundle started: org.apache.felix.configadmin:1.2.8
> 12:19:33,260 INFO  [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-15) Bundle started: org.apache.felix.metatype:1.0.4
> 12:19:33,325 INFO  [org.eclipse.jetty.util.log] (MSC service thread 1-15) jetty-7.x.y-SNAPSHOT
> 12:19:33,363 INFO  [org.eclipse.jetty.util.log] (MSC service thread 1-15) Started [NIOSocketConnectorWrapper at 0.0.0.0:8090]
> 12:19:33,428 INFO  [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-15) Bundle started: jboss-osgi-http:1.0.3
> 12:19:33,438 INFO  [org.eclipse.jetty.util.log] (CM Configuration Updater (ManagedService Update: pid=org.ops4j.pax.web)) jetty-7.x.y-SNAPSHOT
> 12:19:33,440 INFO  [org.eclipse.jetty.util.log] (CM Configuration Updater (ManagedService Update: pid=org.ops4j.pax.web)) Started [NIOSocketConnectorWrapper at 0.0.0.0:8090]

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-osgi-issues mailing list