Hi,
it's a deployment order issue between the WebConsole and Pax Web as it's
installed asynchronously (each in a dedicated thread).
What you can try is to upgrade to Karaf 2.3.3. In the
etc/org.apache.karaf.features.cfg file you will see:
#
# Defines if the boot features are started in asynchronous mode (in a
dedicated thread)
#
featuresBootAsynchronous=false
Be sure that Async is false and define the war feature before the
webconsole feature in featuresBoot.
It should work.
Regards
JB
On 04/03/2014 08:43 AM, SteffeC wrote:
Hi,
I’m working with Karaf 2.3.2 and I’m trying to install the webconsole as a
feature at startup of the container (instead of installing it manually after
login)?
If I SSH into the started container with a terminal, I can see that the
webconsole feature has been installed but I can’t log on with my browser
(http://localhost:8181/system/console/).
This is how it looks when running features:list in the running container:
karaft> features:list
State Version Name Repository
Description
...
[*installed *] [2.3.2 ] webconsole-base karaf-2.3.2
Base support of the Karaf WebConsole
[*installed *] [2.3.2 ] webconsole karaf-2.3.2
Karaf WebConsole for administration and monitoring
[installed ] [2.3.2 ] ssh karaf-2.3.2
Provide a SSHd server on Karaf
[installed ] [2.3.2 ] management karaf-2.3.2
Provide a JMX MBeanServer and a set of MBeans in Karaf
[installed ] [2.3.2 ] eventadmin karaf-2.3.2
OSGi Event Admin service specification for event-based communication
[uninstalled] [2.3.2 ] jasypt-encryption karaf-2.3.2
Advanced encryption support for Karaf security
[*installed *] [2.3.2 ] scr karaf-2.3.2
Declarative Service support
[uninstalled] [2.3.2 ] webconsole-scr karaf-2.3.2
Declarative Service WebConsole plugin support
If I uninstall and reinstall webconsole and webconsole-base from within the
running container, it then works to log on to the container with the
browser.
This is how my POM file and feature calls looks like:
<dependency>
<groupId>org.apache.karaf.assemblies.features</groupId>
<artifactId>enterprise</artifactId>
<version>2.3.2</version>
<classifier>features</classifier>
<type>xml</type>
</dependency>
<dependency>
<groupId>org.apache.karaf.webconsole</groupId>
<artifactId>org.apache.karaf.webconsole.features</artifactId>
<version>2.3.2</version>
</dependency>
public static Option AdditionalFeatures()
{
return composite(
// scr
features(maven()
.groupId("org.apache.karaf.assemblies.features")
.artifactId("enterprise")
.type("xml")
.classifier("features")
.versionAsInProject(),
"scr"),
// webconsole-base
features(maven()
.groupId("org.apache.karaf.webconsole")
.artifactId("org.apache.karaf.webconsole.features")
.versionAsInProject(),
"webconsole-base"),
// webconsole
features(maven()
.groupId("org.apache.karaf.webconsole")
.artifactId("org.apache.karaf.webconsole.features")
.versionAsInProject(),
"webconsole")
);
}
NOTE: I also installed the scr feature and this feature works as expected.
I have tried to find information about this problem on the net and in this
forum but with no luck.
Can anyone explain why the webconsole doesn’t work if I install it at
startup as I describe above?
Is there any log generated when I try to access the container via the
webconsole that can explain what is wrong?
Regards
SteffeC
--
View this message in context:
http://karaf.922171.n3.nabble.com/How-install-webconsole-as-feature-at-startup-of-Karaf-container-tp4032548.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
