AS7 - OSGI Web-Console

[rnair]

Hi,

I am using AS 7.0.2Final and I have trouble starting up the osgi web-console. As per the Admin Guide, I set the subsystem activation level to "eager" and the startlevel to "2". Upon, start up, I get the following error message:

[Server:server-one] 18:59:54,346 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jbosgi.AutoInstallProvider.COMPLETE: org.jboss.msc.service.StartException in service jbosgi.AutoInstallProvider.COMPLETE: Failed to start service

[Server:server-one]     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780)

[Server:server-one]     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]

[Server:server-one]     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]

[Server:server-one]     at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]

[Server:server-one] Caused by: java.lang.IllegalArgumentException: Not a HostBundleState: jbosgi-webconsole:1.0.6

[Server:server-one]     at org.jboss.osgi.framework.internal.HostBundleState.assertBundleState(HostBundleState.java:69)

[Server:server-one]     at org.jboss.osgi.framework.internal.StartLevelPlugin.setBundleStartLevel(StartLevelPlugin.java:165)

[Server:server-one]     at org.jboss.as.osgi.service.AutoInstallIntegration.startBundle(AutoInstallIntegration.java:204)

[Server:server-one]     at org.jboss.as.osgi.service.AutoInstallIntegration$2.start(AutoInstallIntegration.java:147)

[Server:server-one]     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)

[Server:server-one]     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)elp is appreciated.

Any help is appreciated.

[bosschaert]

Hi Reji,

I think for some reason your configuration file has assigned a startlevel to the "org.jboss.osgi.webconsole" module. This module is actually a bundle fragment and should not be assigned a startlevel (at runtime the fragment attaches to the org.apache.felix.webconsole bundle).

The following configuration works fine for me, this is the default config with just activation=eager and <property name="org.osgi.framework.startlevel.beginning">2</property> as changes.

{code:xml}<subsystem xmlns="urn:jboss:domain:osgi:1.0" activation="eager">
    <configuration pid="org.apache.felix.webconsole.internal.servlet.OsgiManager">
        <property name="manager.root">jboss-osgi</property>
    </configuration>
    <properties>
        <!--
            A comma seperated list of module identifiers. Each system module
            is added as a dependency to the OSGi framework module. The packages
            from these system modules can be made visible as framework system packages.
            http://www.osgi.org/javadoc/r4v42/org/osgi/framework/Constants.html#FRAMEWORK_SYSTEMPACKAGES_EXTRA
        -->
        <property name="org.jboss.osgi.system.modules">
        org.apache.commons.logging,
        org.apache.log4j,
        org.jboss.as.osgi,
        org.slf4j,
        </property>
        <!--
            Framework environment property identifying extra packages which the system bundle
            must export from the current execution environment
        -->
        <property name="org.osgi.framework.system.packages.extra">
        org.apache.commons.logging;version=1.1.1,
        org.apache.log4j;version=1.2,
        org.jboss.as.osgi.service;version=7.0,
        org.jboss.osgi.deployment.interceptor;version=1.0,
        org.jboss.osgi.spi.capability;version=1.0,
        org.jboss.osgi.spi.util;version=1.0,
        org.jboss.osgi.testing;version=1.0,
        org.jboss.osgi.vfs;version=1.0,
        org.slf4j;version=1.5.10,
        </property>
        <!-- Specifies the beginning start level of the framework -->
        <property name="org.osgi.framework.startlevel.beginning">2</property>
    </properties>
    <modules>
        <!-- modules registered with the OSGi layer on startup -->
        <module identifier="javaee.api"/>
        <module identifier="org.jboss.logging"/>
        <!-- bundles installed on startup -->
        <module identifier="org.apache.aries.util"/>
        <module identifier="org.jboss.osgi.webconsole"/>
        <module identifier="org.osgi.compendium"/>
        <!-- bundles started in startlevel 1 -->
        <module identifier="org.apache.felix.log" startlevel="1"/>
        <module identifier="org.jboss.osgi.logging" startlevel="1"/>
        <module identifier="org.apache.felix.configadmin" startlevel="1"/>
        <module identifier="org.jboss.as.osgi.configadmin" startlevel="1"/>
        <!-- bundles started in startlevel 2 -->
        <module identifier="org.apache.aries.jmx" startlevel="2"/>
        <module identifier="org.apache.felix.eventadmin" startlevel="2"/>
        <module identifier="org.apache.felix.metatype" startlevel="2"/>
        <module identifier="org.apache.felix.scr" startlevel="2"/>
        <module identifier="org.apache.felix.webconsole" startlevel="2"/>
        <module identifier="org.jboss.osgi.jmx" startlevel="2"/>
        <module identifier="org.jboss.osgi.http" startlevel="2"/>
        <!-- bundles started in startlevel 3 -->
        <module identifier="org.jboss.osgi.blueprint" startlevel="3"/>
        <module identifier="org.jboss.osgi.webapp" startlevel="3"/>
        <module identifier="org.jboss.osgi.xerces" startlevel="3"/>
    </modules>
</subsystem>{code}

You can now access the web console at http://localhost:8090/jboss-osgi (with admin/admin as default login).

Hope this helps,

David

[rnair]

David,

Thank you for your reply. You are correct. I had a start level associated associated to "org.jboss.osgi.webconsole". After correcting this, I still get an error. It looks like this package is missing in 7.0.2Final (not sure). Please note the error:

ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-2) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle: jboss-as-osgi-configadmin:7.0.2.Final
[Server:server-one]     at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8]
[Server:server-one]     at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8]
[Server:server-one]     at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8]
[Server:server-one]     at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8]
[Server:server-one]     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
[Server:server-one]     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
[Server:server-one]     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
[Server:server-one]     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
[Server:server-one]     at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]

Any help is appreciated.

[bosschaert]

Hmmm, I can't seem to reproduce this. I just tried it with freshly downloaded 7.0.2 Final installations (both web and full) and it works fine for me...

Are there any other exceptions that you are seeing on the console? What does your standalone.xml file look like?

[rnair]

David,

I am attaching my domain-preview.xml and the startup log (nohup.out). Hope this can shed some light.

Thanks for your help...

[bosschaert]

Ah yes, that helps. I didn't realize that you were using domain mode. If you use standalone.sh with standalone.xml things should work.

What you're describing is the same as what's described here: JBoss as 7 domain OSGi Web Console

There is a bug for it too: https://issues.jboss.org/browse/AS7-1858

[rnair]

David,

Thanks for your help. I shall look forward to the 7.1Beta1 release.

[jaikiran]

Reji Nair wrote:

I shall look forward to the 7.1Beta1 release.

If you are interested, you can try the nightly binaries of AS7 which should contain that fix http://community.jboss.org/thread/167590