You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by "Uwe K." <Ko...@t-online.de> on 2011/02/14 11:35:33 UTC
Boot-Features not started
Hi,
in the trunk and karaf-2.2.x-versions actually the boot-features aren't
loaded on startup.
You have to connect to the console and issue at least a "feature:list"
command to get them installed.
As I see, the default-activation was changed to "lazy" for the
features/core-bundle (with KARAF-443) .
Am I missing some point, or should this bundle not be loaded in "eager"
mode, to get it started and the boot-features installed?
Kind regards,
Uwe Korte.
--
View this message in context: http://karaf.922171.n3.nabble.com/Boot-Features-not-started-tp2491610p2491610.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: Boot-Features not started
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Thanks :)
Regards
JB
On 02/14/2011 12:27 PM, Guillaume Nodet wrote:
> I've just fixed it.
>
> On Mon, Feb 14, 2011 at 12:16, Jean-Baptiste Onofré<jb...@nanthrax.net> wrote:
>> You're right, I've just made the test.
>>
>> I think that feature should be eager.
>>
>> Let me talk of that with Guillaume as he made the change.
>>
>> Regards
>> JB
>>
>> On 02/14/2011 12:14 PM, Uwe K. wrote:
>>>
>>> Hi Jean-Baptiste,
>>>
>>> config, ssh and management aren't really started by (boot-)feature. Their
>>> bundles (defined in startup.properties) are getting started, not the
>>> features.
>>> You can see that by connecting via console to a freshly installed
>>> instance:
>>> The first time you issue "features:list" all features are "uninstalled".
>>> The
>>> second time (after the features-service started), you can see config, ssh
>>> and management as "installed".
>>>
>>> HTH.
>>>
>>> Kind regards,
>>>
>>> Uwe Korte.
>>>
>>>
>>>
>>> jb-3 wrote:
>>>>
>>>> Hi Uwe,
>>>>
>>>> the startup feature are defined in etc/org.apache.karaf.features.cfg
>>>> file (featuresBoot property).
>>>> I'm surprised as config, ssh and management features are started
>>>> succcessfuly at startup.
>>>> I'm gonna make a try.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 02/14/2011 11:35 AM, Uwe K. wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> in the trunk and karaf-2.2.x-versions actually the boot-features aren't
>>>>> loaded on startup.
>>>>> You have to connect to the console and issue at least a "feature:list"
>>>>> command to get them installed.
>>>>>
>>>>> As I see, the default-activation was changed to "lazy" for the
>>>>> features/core-bundle (with KARAF-443) .
>>>>>
>>>>> Am I missing some point, or should this bundle not be loaded in "eager"
>>>>> mode, to get it started and the boot-features installed?
>>>>>
>>>>> Kind regards,
>>>>>
>>>>> Uwe Korte.
>>>>>
>>>>
>>>>
>>>
>>
>
>
>
Re: Boot-Features not started
Posted by Guillaume Nodet <gn...@gmail.com>.
I've just fixed it.
On Mon, Feb 14, 2011 at 12:16, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> You're right, I've just made the test.
>
> I think that feature should be eager.
>
> Let me talk of that with Guillaume as he made the change.
>
> Regards
> JB
>
> On 02/14/2011 12:14 PM, Uwe K. wrote:
>>
>> Hi Jean-Baptiste,
>>
>> config, ssh and management aren't really started by (boot-)feature. Their
>> bundles (defined in startup.properties) are getting started, not the
>> features.
>> You can see that by connecting via console to a freshly installed
>> instance:
>> The first time you issue "features:list" all features are "uninstalled".
>> The
>> second time (after the features-service started), you can see config, ssh
>> and management as "installed".
>>
>> HTH.
>>
>> Kind regards,
>>
>> Uwe Korte.
>>
>>
>>
>> jb-3 wrote:
>>>
>>> Hi Uwe,
>>>
>>> the startup feature are defined in etc/org.apache.karaf.features.cfg
>>> file (featuresBoot property).
>>> I'm surprised as config, ssh and management features are started
>>> succcessfuly at startup.
>>> I'm gonna make a try.
>>>
>>> Regards
>>> JB
>>>
>>> On 02/14/2011 11:35 AM, Uwe K. wrote:
>>>>
>>>> Hi,
>>>>
>>>> in the trunk and karaf-2.2.x-versions actually the boot-features aren't
>>>> loaded on startup.
>>>> You have to connect to the console and issue at least a "feature:list"
>>>> command to get them installed.
>>>>
>>>> As I see, the default-activation was changed to "lazy" for the
>>>> features/core-bundle (with KARAF-443) .
>>>>
>>>> Am I missing some point, or should this bundle not be loaded in "eager"
>>>> mode, to get it started and the boot-features installed?
>>>>
>>>> Kind regards,
>>>>
>>>> Uwe Korte.
>>>>
>>>
>>>
>>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: Boot-Features not started
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
You're right, I've just made the test.
I think that feature should be eager.
Let me talk of that with Guillaume as he made the change.
Regards
JB
On 02/14/2011 12:14 PM, Uwe K. wrote:
>
> Hi Jean-Baptiste,
>
> config, ssh and management aren't really started by (boot-)feature. Their
> bundles (defined in startup.properties) are getting started, not the
> features.
> You can see that by connecting via console to a freshly installed instance:
> The first time you issue "features:list" all features are "uninstalled". The
> second time (after the features-service started), you can see config, ssh
> and management as "installed".
>
> HTH.
>
> Kind regards,
>
> Uwe Korte.
>
>
>
> jb-3 wrote:
>>
>> Hi Uwe,
>>
>> the startup feature are defined in etc/org.apache.karaf.features.cfg
>> file (featuresBoot property).
>> I'm surprised as config, ssh and management features are started
>> succcessfuly at startup.
>> I'm gonna make a try.
>>
>> Regards
>> JB
>>
>> On 02/14/2011 11:35 AM, Uwe K. wrote:
>>>
>>> Hi,
>>>
>>> in the trunk and karaf-2.2.x-versions actually the boot-features aren't
>>> loaded on startup.
>>> You have to connect to the console and issue at least a "feature:list"
>>> command to get them installed.
>>>
>>> As I see, the default-activation was changed to "lazy" for the
>>> features/core-bundle (with KARAF-443) .
>>>
>>> Am I missing some point, or should this bundle not be loaded in "eager"
>>> mode, to get it started and the boot-features installed?
>>>
>>> Kind regards,
>>>
>>> Uwe Korte.
>>>
>>
>>
>
Re: Boot-Features not started
Posted by "Uwe K." <Ko...@t-online.de>.
Hi Jean-Baptiste,
config, ssh and management aren't really started by (boot-)feature. Their
bundles (defined in startup.properties) are getting started, not the
features.
You can see that by connecting via console to a freshly installed instance:
The first time you issue "features:list" all features are "uninstalled". The
second time (after the features-service started), you can see config, ssh
and management as "installed".
HTH.
Kind regards,
Uwe Korte.
jb-3 wrote:
>
> Hi Uwe,
>
> the startup feature are defined in etc/org.apache.karaf.features.cfg
> file (featuresBoot property).
> I'm surprised as config, ssh and management features are started
> succcessfuly at startup.
> I'm gonna make a try.
>
> Regards
> JB
>
> On 02/14/2011 11:35 AM, Uwe K. wrote:
>>
>> Hi,
>>
>> in the trunk and karaf-2.2.x-versions actually the boot-features aren't
>> loaded on startup.
>> You have to connect to the console and issue at least a "feature:list"
>> command to get them installed.
>>
>> As I see, the default-activation was changed to "lazy" for the
>> features/core-bundle (with KARAF-443) .
>>
>> Am I missing some point, or should this bundle not be loaded in "eager"
>> mode, to get it started and the boot-features installed?
>>
>> Kind regards,
>>
>> Uwe Korte.
>>
>
>
--
View this message in context: http://karaf.922171.n3.nabble.com/Boot-Features-not-started-tp2491610p2491820.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: Boot-Features not started
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Uwe,
the startup feature are defined in etc/org.apache.karaf.features.cfg
file (featuresBoot property).
I'm surprised as config, ssh and management features are started
succcessfuly at startup.
I'm gonna make a try.
Regards
JB
On 02/14/2011 11:35 AM, Uwe K. wrote:
>
> Hi,
>
> in the trunk and karaf-2.2.x-versions actually the boot-features aren't
> loaded on startup.
> You have to connect to the console and issue at least a "feature:list"
> command to get them installed.
>
> As I see, the default-activation was changed to "lazy" for the
> features/core-bundle (with KARAF-443) .
>
> Am I missing some point, or should this bundle not be loaded in "eager"
> mode, to get it started and the boot-features installed?
>
> Kind regards,
>
> Uwe Korte.
>
Re: Boot-Features not started
Posted by jb...@nanthrax.net.
Indeed, with eager loading we haven't the issue. I gonna deal with Guillaume around that.
Regards
JB
-----Original Message-----
From: "Uwe K." <Ko...@t-online.de>
Date: Sat, 19 Feb 2011 11:48:14
To: <de...@karaf.apache.org>
Reply-To: dev@karaf.apache.org
Subject: Re: Boot-Features not started
Hi,
thank you for fixing it so quickly.
But I have another issue:
Same problem, another bundle: the JMX-management-bundle
"org.apache.karaf.admin.management".
When loaded lazy, the MBean is not registered and I see no way to activate
the bundle manually to get the MBean registered.
I know, these functions or not used so often, so if there is a way to
activate the bundle "by hand" (in ssh-console or jconsole) it would be
sufficient. Do you have any tips?
Best regards,
Uwe.
Guillaume Nodet wrote:
>
> I think you're right, features-core should be eager by default. or at
> least the service itself should be eager.
> I'll fix that asap.
>
>
> On Mon, Feb 14, 2011 at 11:35, Uwe K. <Ko...@t-online.de> wrote:
>>
>> Hi,
>>
>> in the trunk and karaf-2.2.x-versions actually the boot-features aren't
>> loaded on startup.
>> You have to connect to the console and issue at least a "feature:list"
>> command to get them installed.
>>
>> As I see, the default-activation was changed to "lazy" for the
>> features/core-bundle (with KARAF-443) .
>>
>> Am I missing some point, or should this bundle not be loaded in "eager"
>> mode, to get it started and the boot-features installed?
>>
>> Kind regards,
>>
>> Uwe Korte.
>>
>> --
>> View this message in context:
>> http://karaf.922171.n3.nabble.com/Boot-Features-not-started-tp2491610p2491610.html
>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
>
--
View this message in context: http://karaf.922171.n3.nabble.com/Boot-Features-not-started-tp2491610p2535298.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: Boot-Features not started
Posted by "Uwe K." <Ko...@t-online.de>.
Hi,
thank you for fixing it so quickly.
But I have another issue:
Same problem, another bundle: the JMX-management-bundle
"org.apache.karaf.admin.management".
When loaded lazy, the MBean is not registered and I see no way to activate
the bundle manually to get the MBean registered.
I know, these functions or not used so often, so if there is a way to
activate the bundle "by hand" (in ssh-console or jconsole) it would be
sufficient. Do you have any tips?
Best regards,
Uwe.
Guillaume Nodet wrote:
>
> I think you're right, features-core should be eager by default. or at
> least the service itself should be eager.
> I'll fix that asap.
>
>
> On Mon, Feb 14, 2011 at 11:35, Uwe K. <Ko...@t-online.de> wrote:
>>
>> Hi,
>>
>> in the trunk and karaf-2.2.x-versions actually the boot-features aren't
>> loaded on startup.
>> You have to connect to the console and issue at least a "feature:list"
>> command to get them installed.
>>
>> As I see, the default-activation was changed to "lazy" for the
>> features/core-bundle (with KARAF-443) .
>>
>> Am I missing some point, or should this bundle not be loaded in "eager"
>> mode, to get it started and the boot-features installed?
>>
>> Kind regards,
>>
>> Uwe Korte.
>>
>> --
>> View this message in context:
>> http://karaf.922171.n3.nabble.com/Boot-Features-not-started-tp2491610p2491610.html
>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
>
--
View this message in context: http://karaf.922171.n3.nabble.com/Boot-Features-not-started-tp2491610p2535298.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: Boot-Features not started
Posted by Guillaume Nodet <gn...@gmail.com>.
I think you're right, features-core should be eager by default. or at
least the service itself should be eager.
I'll fix that asap.
On Mon, Feb 14, 2011 at 11:35, Uwe K. <Ko...@t-online.de> wrote:
>
> Hi,
>
> in the trunk and karaf-2.2.x-versions actually the boot-features aren't
> loaded on startup.
> You have to connect to the console and issue at least a "feature:list"
> command to get them installed.
>
> As I see, the default-activation was changed to "lazy" for the
> features/core-bundle (with KARAF-443) .
>
> Am I missing some point, or should this bundle not be loaded in "eager"
> mode, to get it started and the boot-features installed?
>
> Kind regards,
>
> Uwe Korte.
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Boot-Features-not-started-tp2491610p2491610.html
> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com