You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Jeremy Jongsma <je...@barchart.com> on 2014/02/07 23:27:39 UTC
Boot features no longer starting after 3.0.0.RC1 -> 3.0.0 update
Been scratching my head at this one all day: I just updated our Karaf
version from 3.0.0.RC1 to 3.0.0 today, and all of our integration tests are
failing due to boot features not installing. Has anything big changed
between RC1 and final that would affect boot feature configuration? If I
make no changes except setting the version back to 3.0.0.RC1, it works
perfectly.
During tests I use the maven karaf-assembly packaging goal to build out a
Karaf app layout from the 3.0.0 bundles. It starts up as usual and installs
the features.xml I provide it for the test, but It turns out that none of
the boot features are being activated, so SCR does not activate my
components. Nor can I connect to the console to investigate further what's
going on, because the shell/SSH are not active.
The following messages are showing up in my karaf.log:
INFO | Bundle org.apache.karaf.shell.commands is waiting for namespace
handlers
INFO | Bundle org.apache.karaf.features.command is waiting for namespace
handlers
INFO | Bundle org.apache.karaf.system.command is waiting for namespace
handlers
INFO | Bundle org.apache.karaf.shell.help is waiting for dependencies
[(objectClass=org.apache.felix.service.threadio.ThreadIO)]
INFO | Bundle org.apache.karaf.bundle.command is waiting for namespace
handlers [http://karaf.apache.org/xmlns/shell/v1.1.0]
INFO | Bundle org.apache.karaf.shell.console is waiting for dependencies
[(objectClass=org.apache.felix.service.command.CommandProcessor),
(objectClass=org.apache.felix.service.threadio.ThreadIO)]
Googling has linked this to machines without an internet connection, which
is not the case here.
My etc/org.apache.karaf.features.cfg:
featuresRepositories=mvn:org.apache.karaf.features/standard/3.0.0/xml/features,mvn:org.apache.karaf.features/enterprise/3.0.0/xml/features,mvn:org.ops4j.pax.web/pax-web-features/3.0.5/xml/features,mvn:org.apache.karaf.features/spring/3.0.0/xml/features
featuresBoot=config,standard,region,package,kar,ssh,management,eventadmin,scr
featuresBootAsynchronous=false
Re: Boot features no longer starting after 3.0.0.RC1 -> 3.0.0 update
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Yes, karaf.etc variable (and KARAF_ETC) has been introduced in Karaf
3.0.0 and 2.4.0 (it's a new feature to be able to externalise the etc
folder).
Regards
JB
On 02/11/2014 07:07 PM, Jeremy Jongsma wrote:
> I leave generating the etc/ files to the assembly goal - so those are
> fully updated - but we don't use the bin/ scripts. We execute the main
> class under the Tanuki service wrapper, which means we have define the
> system properties Karaf expects there too. 3.0.0.RC1 apparently did not
> require defining karaf.etc, but 3.0.0 does.
>
>
> On Tue, Feb 11, 2014 at 12:00 PM, Jean-Baptiste Onofré <jb@nanthrax.net
> <ma...@nanthrax.net>> wrote:
>
> Hi Jeremy,
>
> does it mean you didn't update the bin/* scripts or etc/* config file ?
>
> Maybe, you didn't merge but "overwrite" the file.
>
> Regards
> JB
>
> On 02/11/2014 06:45 PM, Jeremy Jongsma wrote:
>
> Thanks, that did it - I didn't notice those log entries.
>
> We're launching Karaf under Tanuki - looks like ${karaf.etc}
> property
> must now be explicitly defined if you're not using the bundled
> startup
> scripts, rather than defaulting to ${karaf.base}/etc (which was RC1
> behavior.)
>
>
> On Mon, Feb 10, 2014 at 10:26 AM, Ryan Moquin
> <fragility2.0@gmail.com <ma...@gmail.com>
> <mailto:fragility2.0@gmail.com
> <ma...@gmail.com>__>> wrote:
>
> I don't think this is a good thing:
>
> Before process:
> file:$(karaf.etc)/org.apache.__karaf.features.cfg
> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
> PropertyPlaceholder | 4 - org.apache.aries.blueprint.__core
> - 1.3.0 |
> Retrieving Value from expression: karaf.etc
>
>
> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
> PropertyPlaceholder | 4 - org.apache.aries.blueprint.__core
> - 1.3.0 |
> Retrieving property karaf.etc
> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
> PropertyPlaceholder | 4 - org.apache.aries.blueprint.__core
> - 1.3.0 |
> Property karaf.etc not found
> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
> AbstractPropertyPlaceholder | 4 -
> org.apache.aries.blueprint.__core -
> 1.3.0 | After process:
> file:$(karaf.etc)/org.apache.__karaf.features.cfg
>
>
> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel |
> PropertyPlaceholder | 4 - org.apache.aries.blueprint.__core
> - 1.3.0 |
> Unable to load properties from url
> file:$(karaf.etc)/org.apache.__karaf.features.cfg while
> ignoreMissingLocations is set to true
>
>
> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel |
> ReferenceRecipe
> | 4 - org.apache.aries.blueprint.__core - 1.3.0 | Unbinding
> reference
> regionsPersistence
> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel |
> ReferenceRecipe
> | 4 - org.apache.aries.blueprint.__core - 1.3.0 | Unbinding
> reference
> configAdmin
> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel |
> ReferenceRecipe
> | 4 - org.apache.aries.blueprint.__core - 1.3.0 | Unbinding
> reference
> mvnUrlHandler
>
>
>
> but anyhow, I see your bundles being referenced in that
> log....
> could you try starting up Karaf without any of your bundles
> deploying? Then you can deploy them after it started and
> that might
> make it easier to diagnose...I think the first thing is to
> get Karaf
> started first without any of your additional bundles/features.
>
> Ryan
>
>
> On Mon, Feb 10, 2014 at 9:53 AM, Jeremy Jongsma
> <jeremy@barchart.com <ma...@barchart.com>
> <mailto:jeremy@barchart.com <ma...@barchart.com>>>
> wrote:
>
> My test machine has full internet access and does have
> access to
> all maven repositories is shows in the logs (maven central,
> sonatype, apache). No artifact retrieval errors are logged.
>
> My karaf.log (at DEBUG level) and
> org.apache.karaf.features.cfg
> are shown here:
>
> https://gist.github.com/__jjongsma/8917280
> <https://gist.github.com/jjongsma/8917280>
>
>
> On Mon, Feb 10, 2014 at 8:36 AM, Ryan Moquin
> <fragility2.0@gmail.com <ma...@gmail.com>
> <mailto:fragility2.0@gmail.com
> <ma...@gmail.com>__>> wrote:
>
> You could set the log level to debug for you start
> it and
> see if it mentions an artifact it can't retrieve..
> not sure
> if it will, but worth a try.
>
> I also had the exact issue a few months ago.. can't
> remember
> what it was.. I thought I had asked about it on here...
> also, looks like you are starting up
> asynchronously, I think
> to avoid problems you need to do it synchronously...
>
> Ryan
>
> On Feb 10, 2014 7:25 AM, "Jean-Baptiste Onofré"
> <jb@nanthrax.net <ma...@nanthrax.net>
> <mailto:jb@nanthrax.net <ma...@nanthrax.net>>> wrote:
>
> Hi
>
> - some boot features artifact are not present
> in the
> system repository (it's a bug and it will be
> fix in 3.0.1)
> - so, Karaf tries to download artifacts from
> internet,
> maybe your Karaf instance doesn't have access
> to Central ?
>
> Regards
> JB
>
> On 02/09/2014 11:44 PM, Jeremy Jongsma wrote:
>
> Just the standard bundled ones I was using
> with RC1:
>
>
> featuresBoot=config,standard,____region,package,kar,ssh,____management,eventadmin,scr
>
>
> On Fri, Feb 7, 2014 at 4:51 PM,
> Jean-Baptiste Onofré
> <jb@nanthrax.net <ma...@nanthrax.net>
> <mailto:jb@nanthrax.net <ma...@nanthrax.net>>
> <mailto:jb@nanthrax.net
> <ma...@nanthrax.net> <mailto:jb@nanthrax.net
> <ma...@nanthrax.net>>>>
> wrote:
>
> Hi Jeremy,
>
> what's the kind of boot features do
> you have ?
> Especially in terms
> of dependency to other features ?
>
> Regards
> JB
>
>
> On 02/07/2014 11:27 PM, Jeremy Jongsma
> wrote:
>
> Been scratching my head at this
> one all
> day: I just updated our
> Karaf
> version from 3.0.0.RC1 to 3.0.0
> today, and
> all of our
> integration tests
> are failing due to boot features not
> installing. Has anything big
> changed between RC1 and final that
> would
> affect boot feature
> configuration? If I make no
> changes except
> setting the version
> back to
> 3.0.0.RC1, it works perfectly.
>
> During tests I use the maven
> karaf-assembly
> packaging goal to
> build out
> a Karaf app layout from the 3.0.0
> bundles.
> It starts up as usual and
> installs the features.xml I
> provide it for
> the test, but It
> turns out
> that none of the boot features are
> being
> activated, so SCR does not
> activate my components. Nor can I
> connect
> to the console to
> investigate
> further what's going on, because the
> shell/SSH are not active.
>
> The following messages are showing
> up in my
> karaf.log:
>
> INFO | Bundle
> org.apache.karaf.shell.______commands is
> waiting for
> namespace
> handlers
> INFO | Bundle
> org.apache.karaf.features.______command is
> waiting for
> namespace handlers
> INFO | Bundle
> org.apache.karaf.system.______command is
> waiting for
> namespace
> handlers
> INFO | Bundle
> org.apache.karaf.shell.help
> is waiting for
> dependencies
>
>
> [(objectClass=org.apache.______felix.service.threadio.______ThreadIO)]
> INFO | Bundle
> org.apache.karaf.bundle.______command is
> waiting for
> namespace
> handlers
>
> [http://karaf.apache.org/______xmlns/shell/v1.1.0
> <http://karaf.apache.org/____xmlns/shell/v1.1.0>
>
> <http://karaf.apache.org/____xmlns/shell/v1.1.0
> <http://karaf.apache.org/__xmlns/shell/v1.1.0>>
>
>
> <http://karaf.apache.org/____xmlns/shell/v1.1.0
> <http://karaf.apache.org/__xmlns/shell/v1.1.0>
>
> <http://karaf.apache.org/__xmlns/shell/v1.1.0
> <http://karaf.apache.org/xmlns/shell/v1.1.0>>>]
> INFO | Bundle
> org.apache.karaf.shell.console is waiting for
> dependencies
>
>
> [(objectClass=org.apache.______felix.service.command.______CommandProcessor),
>
>
> (objectClass=org.apache.felix.______service.threadio.ThreadIO)__]
>
> Googling has linked this to machines
> without an internet connection,
> which is not the case here.
>
> My
> etc/org.apache.karaf.features.______cfg:
>
>
>
> featuresRepositories=mvn:org.______apache.karaf.features/______standard/3.0.0/xml/features,______mvn:org.apache.karaf.__features/____enterprise/3.0.0/__xml/__features,__mvn:org.__ops4j.pax.__web/pax-web-____features/3.0.5/__xml/features,____mvn:org.apache.__karaf.__features/__spring/3.0.0/__xml/__features
>
>
>
> featuresBoot=config,standard,______region,package,kar,ssh,______management,eventadmin,scr
>
> featuresBootAsynchronous=false
>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> <mailto:jbonofre@apache.org <ma...@apache.org>>
> <mailto:jbonofre@apache.org
> <ma...@apache.org>
> <mailto:jbonofre@apache.org
> <ma...@apache.org>>>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> <mailto:jbonofre@apache.org <ma...@apache.org>>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
>
>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Boot features no longer starting after 3.0.0.RC1 -> 3.0.0 update
Posted by Jeremy Jongsma <je...@barchart.com>.
I leave generating the etc/ files to the assembly goal - so those are fully
updated - but we don't use the bin/ scripts. We execute the main class
under the Tanuki service wrapper, which means we have define the system
properties Karaf expects there too. 3.0.0.RC1 apparently did not require
defining karaf.etc, but 3.0.0 does.
On Tue, Feb 11, 2014 at 12:00 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> Hi Jeremy,
>
> does it mean you didn't update the bin/* scripts or etc/* config file ?
>
> Maybe, you didn't merge but "overwrite" the file.
>
> Regards
> JB
>
> On 02/11/2014 06:45 PM, Jeremy Jongsma wrote:
>
>> Thanks, that did it - I didn't notice those log entries.
>>
>> We're launching Karaf under Tanuki - looks like ${karaf.etc} property
>> must now be explicitly defined if you're not using the bundled startup
>> scripts, rather than defaulting to ${karaf.base}/etc (which was RC1
>> behavior.)
>>
>>
>> On Mon, Feb 10, 2014 at 10:26 AM, Ryan Moquin <fragility2.0@gmail.com
>> <ma...@gmail.com>> wrote:
>>
>> I don't think this is a good thing:
>>
>> Before process: file:$(karaf.etc)/org.apache.karaf.features.cfg
>> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
>> PropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 |
>> Retrieving Value from expression: karaf.etc
>>
>>
>> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
>> PropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 |
>> Retrieving property karaf.etc
>> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
>> PropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 |
>> Property karaf.etc not found
>> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
>> AbstractPropertyPlaceholder | 4 - org.apache.aries.blueprint.core -
>> 1.3.0 | After process: file:$(karaf.etc)/org.apache.
>> karaf.features.cfg
>>
>>
>> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel |
>> PropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 |
>> Unable to load properties from url
>> file:$(karaf.etc)/org.apache.karaf.features.cfg while
>> ignoreMissingLocations is set to true
>>
>>
>> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | ReferenceRecipe
>> | 4 - org.apache.aries.blueprint.core - 1.3.0 | Unbinding reference
>> regionsPersistence
>> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | ReferenceRecipe
>> | 4 - org.apache.aries.blueprint.core - 1.3.0 | Unbinding reference
>> configAdmin
>> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | ReferenceRecipe
>> | 4 - org.apache.aries.blueprint.core - 1.3.0 | Unbinding reference
>> mvnUrlHandler
>>
>>
>>
>> but anyhow, I see your bundles being referenced in that log....
>> could you try starting up Karaf without any of your bundles
>> deploying? Then you can deploy them after it started and that might
>> make it easier to diagnose...I think the first thing is to get Karaf
>> started first without any of your additional bundles/features.
>>
>> Ryan
>>
>>
>> On Mon, Feb 10, 2014 at 9:53 AM, Jeremy Jongsma <jeremy@barchart.com
>> <ma...@barchart.com>> wrote:
>>
>> My test machine has full internet access and does have access to
>> all maven repositories is shows in the logs (maven central,
>> sonatype, apache). No artifact retrieval errors are logged.
>>
>> My karaf.log (at DEBUG level) and org.apache.karaf.features.cfg
>> are shown here:
>>
>> https://gist.github.com/jjongsma/8917280
>>
>>
>> On Mon, Feb 10, 2014 at 8:36 AM, Ryan Moquin
>> <fragility2.0@gmail.com <ma...@gmail.com>> wrote:
>>
>> You could set the log level to debug for you start it and
>> see if it mentions an artifact it can't retrieve.. not sure
>> if it will, but worth a try.
>>
>> I also had the exact issue a few months ago.. can't remember
>> what it was.. I thought I had asked about it on here...
>> also, looks like you are starting up asynchronously, I think
>> to avoid problems you need to do it synchronously...
>>
>> Ryan
>>
>> On Feb 10, 2014 7:25 AM, "Jean-Baptiste Onofré"
>> <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>>
>> Hi
>>
>> - some boot features artifact are not present in the
>> system repository (it's a bug and it will be fix in 3.0.1)
>> - so, Karaf tries to download artifacts from internet,
>> maybe your Karaf instance doesn't have access to Central ?
>>
>> Regards
>> JB
>>
>> On 02/09/2014 11:44 PM, Jeremy Jongsma wrote:
>>
>> Just the standard bundled ones I was using with RC1:
>>
>> featuresBoot=config,standard,_
>> _region,package,kar,ssh,__management,eventadmin,scr
>>
>>
>> On Fri, Feb 7, 2014 at 4:51 PM, Jean-Baptiste Onofré
>> <jb@nanthrax.net <ma...@nanthrax.net>
>> <mailto:jb@nanthrax.net <ma...@nanthrax.net>>>
>> wrote:
>>
>> Hi Jeremy,
>>
>> what's the kind of boot features do you have ?
>> Especially in terms
>> of dependency to other features ?
>>
>> Regards
>> JB
>>
>>
>> On 02/07/2014 11:27 PM, Jeremy Jongsma wrote:
>>
>> Been scratching my head at this one all
>> day: I just updated our
>> Karaf
>> version from 3.0.0.RC1 to 3.0.0 today, and
>> all of our
>> integration tests
>> are failing due to boot features not
>> installing. Has anything big
>> changed between RC1 and final that would
>> affect boot feature
>> configuration? If I make no changes except
>> setting the version
>> back to
>> 3.0.0.RC1, it works perfectly.
>>
>> During tests I use the maven karaf-assembly
>> packaging goal to
>> build out
>> a Karaf app layout from the 3.0.0 bundles.
>> It starts up as usual and
>> installs the features.xml I provide it for
>> the test, but It
>> turns out
>> that none of the boot features are being
>> activated, so SCR does not
>> activate my components. Nor can I connect
>> to the console to
>> investigate
>> further what's going on, because the
>> shell/SSH are not active.
>>
>> The following messages are showing up in my
>> karaf.log:
>>
>> INFO | Bundle
>> org.apache.karaf.shell.____commands is waiting for
>> namespace
>> handlers
>> INFO | Bundle
>> org.apache.karaf.features.____command is waiting for
>> namespace handlers
>> INFO | Bundle
>> org.apache.karaf.system.____command is waiting for
>> namespace
>> handlers
>> INFO | Bundle org.apache.karaf.shell.help
>> is waiting for
>> dependencies
>>
>> [(objectClass=org.apache.____
>> felix.service.threadio.____ThreadIO)]
>> INFO | Bundle
>> org.apache.karaf.bundle.____command is waiting for
>> namespace
>> handlers
>> [http://karaf.apache.org/____xmlns/shell/v1.1.0
>> <http://karaf.apache.org/__xmlns/shell/v1.1.0>
>>
>> <http://karaf.apache.org/__xmlns/shell/v1.1.0
>> <http://karaf.apache.org/xmlns/shell/v1.1.0>>]
>> INFO | Bundle
>> org.apache.karaf.shell.console is waiting for
>> dependencies
>>
>> [(objectClass=org.apache.____
>> felix.service.command.____CommandProcessor),
>>
>> (objectClass=org.apache.felix.
>> ____service.threadio.ThreadIO)]
>>
>> Googling has linked this to machines
>> without an internet connection,
>> which is not the case here.
>>
>> My etc/org.apache.karaf.features.____cfg:
>>
>>
>> featuresRepositories=mvn:org._
>> ___apache.karaf.features/____standard/3.0.0/xml/features,__
>> __mvn:org.apache.karaf.features/____enterprise/3.0.0/
>> xml/__features,__mvn:org.ops4j.pax.__web/pax-web-__
>> features/3.0.5/__xml/features,__mvn:org.apache.__karaf.
>> features/__spring/3.0.0/__xml/features
>>
>>
>> featuresBoot=config,standard,_
>> ___region,package,kar,ssh,____management,eventadmin,scr
>>
>> featuresBootAsynchronous=false
>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org <ma...@apache.org>
>> <mailto:jbonofre@apache.org
>> <ma...@apache.org>>
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org <ma...@apache.org>
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>>
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Boot features no longer starting after 3.0.0.RC1 -> 3.0.0 update
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Jeremy,
does it mean you didn't update the bin/* scripts or etc/* config file ?
Maybe, you didn't merge but "overwrite" the file.
Regards
JB
On 02/11/2014 06:45 PM, Jeremy Jongsma wrote:
> Thanks, that did it - I didn't notice those log entries.
>
> We're launching Karaf under Tanuki - looks like ${karaf.etc} property
> must now be explicitly defined if you're not using the bundled startup
> scripts, rather than defaulting to ${karaf.base}/etc (which was RC1
> behavior.)
>
>
> On Mon, Feb 10, 2014 at 10:26 AM, Ryan Moquin <fragility2.0@gmail.com
> <ma...@gmail.com>> wrote:
>
> I don't think this is a good thing:
>
> Before process: file:$(karaf.etc)/org.apache.karaf.features.cfg
> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
> PropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 |
> Retrieving Value from expression: karaf.etc
>
>
> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
> PropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 |
> Retrieving property karaf.etc
> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
> PropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 |
> Property karaf.etc not found
> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
> AbstractPropertyPlaceholder | 4 - org.apache.aries.blueprint.core -
> 1.3.0 | After process: file:$(karaf.etc)/org.apache.karaf.features.cfg
>
>
> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel |
> PropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 |
> Unable to load properties from url
> file:$(karaf.etc)/org.apache.karaf.features.cfg while
> ignoreMissingLocations is set to true
>
>
> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | ReferenceRecipe
> | 4 - org.apache.aries.blueprint.core - 1.3.0 | Unbinding reference
> regionsPersistence
> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | ReferenceRecipe
> | 4 - org.apache.aries.blueprint.core - 1.3.0 | Unbinding reference
> configAdmin
> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | ReferenceRecipe
> | 4 - org.apache.aries.blueprint.core - 1.3.0 | Unbinding reference
> mvnUrlHandler
>
>
>
> but anyhow, I see your bundles being referenced in that log....
> could you try starting up Karaf without any of your bundles
> deploying? Then you can deploy them after it started and that might
> make it easier to diagnose...I think the first thing is to get Karaf
> started first without any of your additional bundles/features.
>
> Ryan
>
>
> On Mon, Feb 10, 2014 at 9:53 AM, Jeremy Jongsma <jeremy@barchart.com
> <ma...@barchart.com>> wrote:
>
> My test machine has full internet access and does have access to
> all maven repositories is shows in the logs (maven central,
> sonatype, apache). No artifact retrieval errors are logged.
>
> My karaf.log (at DEBUG level) and org.apache.karaf.features.cfg
> are shown here:
>
> https://gist.github.com/jjongsma/8917280
>
>
> On Mon, Feb 10, 2014 at 8:36 AM, Ryan Moquin
> <fragility2.0@gmail.com <ma...@gmail.com>> wrote:
>
> You could set the log level to debug for you start it and
> see if it mentions an artifact it can't retrieve.. not sure
> if it will, but worth a try.
>
> I also had the exact issue a few months ago.. can't remember
> what it was.. I thought I had asked about it on here...
> also, looks like you are starting up asynchronously, I think
> to avoid problems you need to do it synchronously...
>
> Ryan
>
> On Feb 10, 2014 7:25 AM, "Jean-Baptiste Onofré"
> <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>
> Hi
>
> - some boot features artifact are not present in the
> system repository (it's a bug and it will be fix in 3.0.1)
> - so, Karaf tries to download artifacts from internet,
> maybe your Karaf instance doesn't have access to Central ?
>
> Regards
> JB
>
> On 02/09/2014 11:44 PM, Jeremy Jongsma wrote:
>
> Just the standard bundled ones I was using with RC1:
>
> featuresBoot=config,standard,__region,package,kar,ssh,__management,eventadmin,scr
>
>
> On Fri, Feb 7, 2014 at 4:51 PM, Jean-Baptiste Onofré
> <jb@nanthrax.net <ma...@nanthrax.net>
> <mailto:jb@nanthrax.net <ma...@nanthrax.net>>>
> wrote:
>
> Hi Jeremy,
>
> what's the kind of boot features do you have ?
> Especially in terms
> of dependency to other features ?
>
> Regards
> JB
>
>
> On 02/07/2014 11:27 PM, Jeremy Jongsma wrote:
>
> Been scratching my head at this one all
> day: I just updated our
> Karaf
> version from 3.0.0.RC1 to 3.0.0 today, and
> all of our
> integration tests
> are failing due to boot features not
> installing. Has anything big
> changed between RC1 and final that would
> affect boot feature
> configuration? If I make no changes except
> setting the version
> back to
> 3.0.0.RC1, it works perfectly.
>
> During tests I use the maven karaf-assembly
> packaging goal to
> build out
> a Karaf app layout from the 3.0.0 bundles.
> It starts up as usual and
> installs the features.xml I provide it for
> the test, but It
> turns out
> that none of the boot features are being
> activated, so SCR does not
> activate my components. Nor can I connect
> to the console to
> investigate
> further what's going on, because the
> shell/SSH are not active.
>
> The following messages are showing up in my
> karaf.log:
>
> INFO | Bundle
> org.apache.karaf.shell.____commands is waiting for
> namespace
> handlers
> INFO | Bundle
> org.apache.karaf.features.____command is waiting for
> namespace handlers
> INFO | Bundle
> org.apache.karaf.system.____command is waiting for
> namespace
> handlers
> INFO | Bundle org.apache.karaf.shell.help
> is waiting for
> dependencies
>
> [(objectClass=org.apache.____felix.service.threadio.____ThreadIO)]
> INFO | Bundle
> org.apache.karaf.bundle.____command is waiting for
> namespace
> handlers
> [http://karaf.apache.org/____xmlns/shell/v1.1.0
> <http://karaf.apache.org/__xmlns/shell/v1.1.0>
>
> <http://karaf.apache.org/__xmlns/shell/v1.1.0
> <http://karaf.apache.org/xmlns/shell/v1.1.0>>]
> INFO | Bundle
> org.apache.karaf.shell.console is waiting for
> dependencies
>
> [(objectClass=org.apache.____felix.service.command.____CommandProcessor),
>
> (objectClass=org.apache.felix.____service.threadio.ThreadIO)]
>
> Googling has linked this to machines
> without an internet connection,
> which is not the case here.
>
> My etc/org.apache.karaf.features.____cfg:
>
>
> featuresRepositories=mvn:org.____apache.karaf.features/____standard/3.0.0/xml/features,____mvn:org.apache.karaf.features/____enterprise/3.0.0/xml/__features,__mvn:org.ops4j.pax.__web/pax-web-__features/3.0.5/__xml/features,__mvn:org.apache.__karaf.features/__spring/3.0.0/__xml/features
>
>
> featuresBoot=config,standard,____region,package,kar,ssh,____management,eventadmin,scr
>
> featuresBootAsynchronous=false
>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> <mailto:jbonofre@apache.org
> <ma...@apache.org>>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Boot features no longer starting after 3.0.0.RC1 -> 3.0.0 update
Posted by Jeremy Jongsma <je...@barchart.com>.
Thanks, that did it - I didn't notice those log entries.
We're launching Karaf under Tanuki - looks like ${karaf.etc} property must
now be explicitly defined if you're not using the bundled startup scripts,
rather than defaulting to ${karaf.base}/etc (which was RC1 behavior.)
On Mon, Feb 10, 2014 at 10:26 AM, Ryan Moquin <fr...@gmail.com>wrote:
> I don't think this is a good thing:
>
> Before process: file:$(karaf.etc)/org.apache.karaf.features.cfg
> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel | PropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 | Retrieving Value from expression: karaf.etc
> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel | PropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 | Retrieving property karaf.etc
>
> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel | PropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 | Property karaf.etc not found
> 2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel | AbstractPropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 | After process: file:$(karaf.etc)/org.apache.karaf.features.cfg
> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | PropertyPlaceholder | 4 - org.apache.aries.blueprint.core - 1.3.0 | Unable to load properties from url file:$(karaf.etc)/org.apache.karaf.features.cfg while ignoreMissingLocations is set to true
> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | ReferenceRecipe | 4 - org.apache.aries.blueprint.core - 1.3.0 | Unbinding reference regionsPersistence
>
> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | ReferenceRecipe | 4 - org.apache.aries.blueprint.core - 1.3.0 | Unbinding reference configAdmin
> 2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | ReferenceRecipe | 4 - org.apache.aries.blueprint.core - 1.3.0 | Unbinding reference mvnUrlHandler
>
>
> but anyhow, I see your bundles being referenced in that log.... could you
> try starting up Karaf without any of your bundles deploying? Then you can
> deploy them after it started and that might make it easier to diagnose...I
> think the first thing is to get Karaf started first without any of your
> additional bundles/features.
>
> Ryan
>
>
> On Mon, Feb 10, 2014 at 9:53 AM, Jeremy Jongsma <je...@barchart.com>wrote:
>
>> My test machine has full internet access and does have access to all
>> maven repositories is shows in the logs (maven central, sonatype, apache).
>> No artifact retrieval errors are logged.
>>
>> My karaf.log (at DEBUG level) and org.apache.karaf.features.cfg are shown
>> here:
>>
>> https://gist.github.com/jjongsma/8917280
>>
>>
>> On Mon, Feb 10, 2014 at 8:36 AM, Ryan Moquin <fr...@gmail.com>wrote:
>>
>>> You could set the log level to debug for you start it and see if it
>>> mentions an artifact it can't retrieve.. not sure if it will, but worth a
>>> try.
>>>
>>> I also had the exact issue a few months ago.. can't remember what it
>>> was.. I thought I had asked about it on here... also, looks like you are
>>> starting up asynchronously, I think to avoid problems you need to do it
>>> synchronously...
>>>
>>> Ryan
>>> On Feb 10, 2014 7:25 AM, "Jean-Baptiste Onofré" <jb...@nanthrax.net> wrote:
>>>
>>>> Hi
>>>>
>>>> - some boot features artifact are not present in the system repository
>>>> (it's a bug and it will be fix in 3.0.1)
>>>> - so, Karaf tries to download artifacts from internet, maybe your Karaf
>>>> instance doesn't have access to Central ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 02/09/2014 11:44 PM, Jeremy Jongsma wrote:
>>>>
>>>>> Just the standard bundled ones I was using with RC1:
>>>>>
>>>>> featuresBoot=config,standard,region,package,kar,ssh,
>>>>> management,eventadmin,scr
>>>>>
>>>>>
>>>>> On Fri, Feb 7, 2014 at 4:51 PM, Jean-Baptiste Onofré <jb@nanthrax.net
>>>>> <ma...@nanthrax.net>> wrote:
>>>>>
>>>>> Hi Jeremy,
>>>>>
>>>>> what's the kind of boot features do you have ? Especially in terms
>>>>> of dependency to other features ?
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>>
>>>>> On 02/07/2014 11:27 PM, Jeremy Jongsma wrote:
>>>>>
>>>>> Been scratching my head at this one all day: I just updated our
>>>>> Karaf
>>>>> version from 3.0.0.RC1 to 3.0.0 today, and all of our
>>>>> integration tests
>>>>> are failing due to boot features not installing. Has anything
>>>>> big
>>>>> changed between RC1 and final that would affect boot feature
>>>>> configuration? If I make no changes except setting the version
>>>>> back to
>>>>> 3.0.0.RC1, it works perfectly.
>>>>>
>>>>> During tests I use the maven karaf-assembly packaging goal to
>>>>> build out
>>>>> a Karaf app layout from the 3.0.0 bundles. It starts up as
>>>>> usual and
>>>>> installs the features.xml I provide it for the test, but It
>>>>> turns out
>>>>> that none of the boot features are being activated, so SCR
>>>>> does not
>>>>> activate my components. Nor can I connect to the console to
>>>>> investigate
>>>>> further what's going on, because the shell/SSH are not active.
>>>>>
>>>>> The following messages are showing up in my karaf.log:
>>>>>
>>>>> INFO | Bundle org.apache.karaf.shell.__commands is waiting
>>>>> for
>>>>> namespace
>>>>> handlers
>>>>> INFO | Bundle org.apache.karaf.features.__command is waiting
>>>>> for
>>>>> namespace handlers
>>>>> INFO | Bundle org.apache.karaf.system.__command is waiting
>>>>> for
>>>>> namespace
>>>>> handlers
>>>>> INFO | Bundle org.apache.karaf.shell.help is waiting for
>>>>> dependencies
>>>>> [(objectClass=org.apache.__felix.service.threadio.__ThreadIO)]
>>>>> INFO | Bundle org.apache.karaf.bundle.__command is waiting
>>>>> for
>>>>> namespace
>>>>> handlers [http://karaf.apache.org/__xmlns/shell/v1.1.0
>>>>> <http://karaf.apache.org/xmlns/shell/v1.1.0>]
>>>>> INFO | Bundle org.apache.karaf.shell.console is waiting for
>>>>> dependencies
>>>>> [(objectClass=org.apache.__felix.service.command.__
>>>>> CommandProcessor),
>>>>> (objectClass=org.apache.felix.__service.threadio.ThreadIO)]
>>>>>
>>>>> Googling has linked this to machines without an internet
>>>>> connection,
>>>>> which is not the case here.
>>>>>
>>>>> My etc/org.apache.karaf.features.__cfg:
>>>>>
>>>>> featuresRepositories=mvn:org.__apache.karaf.features/__
>>>>> standard/3.0.0/xml/features,__mvn:org.apache.karaf.features/
>>>>> __enterprise/3.0.0/xml/features,__mvn:org.ops4j.pax.
>>>>> web/pax-web-__features/3.0.5/xml/features,__mvn:org.apache.
>>>>> karaf.features/__spring/3.0.0/xml/features
>>>>>
>>>>> featuresBoot=config,standard,__region,package,kar,ssh,__
>>>>> management,eventadmin,scr
>>>>>
>>>>> featuresBootAsynchronous=false
>>>>>
>>>>>
>>>>> --
>>>>> Jean-Baptiste Onofré
>>>>> jbonofre@apache.org <ma...@apache.org>
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>>
>>>>>
>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>
>>
>
Re: Boot features no longer starting after 3.0.0.RC1 -> 3.0.0 update
Posted by Ryan Moquin <fr...@gmail.com>.
I don't think this is a good thing:
Before process: file:$(karaf.etc)/org.apache.karaf.features.cfg
2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
PropertyPlaceholder | 4 - org.apache.aries.blueprint.core
- 1.3.0 | Retrieving Value from expression: karaf.etc
2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
PropertyPlaceholder | 4 - org.apache.aries.blueprint.core
- 1.3.0 | Retrieving property karaf.etc
2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
PropertyPlaceholder | 4 - org.apache.aries.blueprint.core
- 1.3.0 | Property karaf.etc not found
2014-02-10 08:47:24,817 | DEBUG | FelixStartLevel |
AbstractPropertyPlaceholder | 4 - org.apache.aries.blueprint.core
- 1.3.0 | After process:
file:$(karaf.etc)/org.apache.karaf.features.cfg
2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel |
PropertyPlaceholder | 4 - org.apache.aries.blueprint.core
- 1.3.0 | Unable to load properties from url
file:$(karaf.etc)/org.apache.karaf.features.cfg while
ignoreMissingLocations is set to true
2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | ReferenceRecipe
| 4 - org.apache.aries.blueprint.core - 1.3.0 |
Unbinding reference regionsPersistence
2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | ReferenceRecipe
| 4 - org.apache.aries.blueprint.core - 1.3.0 |
Unbinding reference configAdmin
2014-02-10 08:47:24,819 | DEBUG | FelixStartLevel | ReferenceRecipe
| 4 - org.apache.aries.blueprint.core - 1.3.0 |
Unbinding reference mvnUrlHandler
but anyhow, I see your bundles being referenced in that log.... could you
try starting up Karaf without any of your bundles deploying? Then you can
deploy them after it started and that might make it easier to diagnose...I
think the first thing is to get Karaf started first without any of your
additional bundles/features.
Ryan
On Mon, Feb 10, 2014 at 9:53 AM, Jeremy Jongsma <je...@barchart.com> wrote:
> My test machine has full internet access and does have access to all maven
> repositories is shows in the logs (maven central, sonatype, apache). No
> artifact retrieval errors are logged.
>
> My karaf.log (at DEBUG level) and org.apache.karaf.features.cfg are shown
> here:
>
> https://gist.github.com/jjongsma/8917280
>
>
> On Mon, Feb 10, 2014 at 8:36 AM, Ryan Moquin <fr...@gmail.com>wrote:
>
>> You could set the log level to debug for you start it and see if it
>> mentions an artifact it can't retrieve.. not sure if it will, but worth a
>> try.
>>
>> I also had the exact issue a few months ago.. can't remember what it
>> was.. I thought I had asked about it on here... also, looks like you are
>> starting up asynchronously, I think to avoid problems you need to do it
>> synchronously...
>>
>> Ryan
>> On Feb 10, 2014 7:25 AM, "Jean-Baptiste Onofré" <jb...@nanthrax.net> wrote:
>>
>>> Hi
>>>
>>> - some boot features artifact are not present in the system repository
>>> (it's a bug and it will be fix in 3.0.1)
>>> - so, Karaf tries to download artifacts from internet, maybe your Karaf
>>> instance doesn't have access to Central ?
>>>
>>> Regards
>>> JB
>>>
>>> On 02/09/2014 11:44 PM, Jeremy Jongsma wrote:
>>>
>>>> Just the standard bundled ones I was using with RC1:
>>>>
>>>> featuresBoot=config,standard,region,package,kar,ssh,
>>>> management,eventadmin,scr
>>>>
>>>>
>>>> On Fri, Feb 7, 2014 at 4:51 PM, Jean-Baptiste Onofré <jb@nanthrax.net
>>>> <ma...@nanthrax.net>> wrote:
>>>>
>>>> Hi Jeremy,
>>>>
>>>> what's the kind of boot features do you have ? Especially in terms
>>>> of dependency to other features ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>> On 02/07/2014 11:27 PM, Jeremy Jongsma wrote:
>>>>
>>>> Been scratching my head at this one all day: I just updated our
>>>> Karaf
>>>> version from 3.0.0.RC1 to 3.0.0 today, and all of our
>>>> integration tests
>>>> are failing due to boot features not installing. Has anything
>>>> big
>>>> changed between RC1 and final that would affect boot feature
>>>> configuration? If I make no changes except setting the version
>>>> back to
>>>> 3.0.0.RC1, it works perfectly.
>>>>
>>>> During tests I use the maven karaf-assembly packaging goal to
>>>> build out
>>>> a Karaf app layout from the 3.0.0 bundles. It starts up as
>>>> usual and
>>>> installs the features.xml I provide it for the test, but It
>>>> turns out
>>>> that none of the boot features are being activated, so SCR does
>>>> not
>>>> activate my components. Nor can I connect to the console to
>>>> investigate
>>>> further what's going on, because the shell/SSH are not active.
>>>>
>>>> The following messages are showing up in my karaf.log:
>>>>
>>>> INFO | Bundle org.apache.karaf.shell.__commands is waiting for
>>>> namespace
>>>> handlers
>>>> INFO | Bundle org.apache.karaf.features.__command is waiting
>>>> for
>>>> namespace handlers
>>>> INFO | Bundle org.apache.karaf.system.__command is waiting for
>>>> namespace
>>>> handlers
>>>> INFO | Bundle org.apache.karaf.shell.help is waiting for
>>>> dependencies
>>>> [(objectClass=org.apache.__felix.service.threadio.__ThreadIO)]
>>>> INFO | Bundle org.apache.karaf.bundle.__command is waiting for
>>>> namespace
>>>> handlers [http://karaf.apache.org/__xmlns/shell/v1.1.0
>>>> <http://karaf.apache.org/xmlns/shell/v1.1.0>]
>>>> INFO | Bundle org.apache.karaf.shell.console is waiting for
>>>> dependencies
>>>> [(objectClass=org.apache.__felix.service.command.__
>>>> CommandProcessor),
>>>> (objectClass=org.apache.felix.__service.threadio.ThreadIO)]
>>>>
>>>> Googling has linked this to machines without an internet
>>>> connection,
>>>> which is not the case here.
>>>>
>>>> My etc/org.apache.karaf.features.__cfg:
>>>>
>>>> featuresRepositories=mvn:org.__apache.karaf.features/__
>>>> standard/3.0.0/xml/features,__mvn:org.apache.karaf.features/
>>>> __enterprise/3.0.0/xml/features,__mvn:org.ops4j.pax.
>>>> web/pax-web-__features/3.0.5/xml/features,__mvn:org.apache.
>>>> karaf.features/__spring/3.0.0/xml/features
>>>>
>>>> featuresBoot=config,standard,__region,package,kar,ssh,__
>>>> management,eventadmin,scr
>>>>
>>>> featuresBootAsynchronous=false
>>>>
>>>>
>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@apache.org <ma...@apache.org>
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>
Re: Boot features no longer starting after 3.0.0.RC1 -> 3.0.0 update
Posted by Jeremy Jongsma <je...@barchart.com>.
My test machine has full internet access and does have access to all maven
repositories is shows in the logs (maven central, sonatype, apache). No
artifact retrieval errors are logged.
My karaf.log (at DEBUG level) and org.apache.karaf.features.cfg are shown
here:
https://gist.github.com/jjongsma/8917280
On Mon, Feb 10, 2014 at 8:36 AM, Ryan Moquin <fr...@gmail.com> wrote:
> You could set the log level to debug for you start it and see if it
> mentions an artifact it can't retrieve.. not sure if it will, but worth a
> try.
>
> I also had the exact issue a few months ago.. can't remember what it was..
> I thought I had asked about it on here... also, looks like you are
> starting up asynchronously, I think to avoid problems you need to do it
> synchronously...
>
> Ryan
> On Feb 10, 2014 7:25 AM, "Jean-Baptiste Onofré" <jb...@nanthrax.net> wrote:
>
>> Hi
>>
>> - some boot features artifact are not present in the system repository
>> (it's a bug and it will be fix in 3.0.1)
>> - so, Karaf tries to download artifacts from internet, maybe your Karaf
>> instance doesn't have access to Central ?
>>
>> Regards
>> JB
>>
>> On 02/09/2014 11:44 PM, Jeremy Jongsma wrote:
>>
>>> Just the standard bundled ones I was using with RC1:
>>>
>>> featuresBoot=config,standard,region,package,kar,ssh,
>>> management,eventadmin,scr
>>>
>>>
>>> On Fri, Feb 7, 2014 at 4:51 PM, Jean-Baptiste Onofré <jb@nanthrax.net
>>> <ma...@nanthrax.net>> wrote:
>>>
>>> Hi Jeremy,
>>>
>>> what's the kind of boot features do you have ? Especially in terms
>>> of dependency to other features ?
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 02/07/2014 11:27 PM, Jeremy Jongsma wrote:
>>>
>>> Been scratching my head at this one all day: I just updated our
>>> Karaf
>>> version from 3.0.0.RC1 to 3.0.0 today, and all of our
>>> integration tests
>>> are failing due to boot features not installing. Has anything big
>>> changed between RC1 and final that would affect boot feature
>>> configuration? If I make no changes except setting the version
>>> back to
>>> 3.0.0.RC1, it works perfectly.
>>>
>>> During tests I use the maven karaf-assembly packaging goal to
>>> build out
>>> a Karaf app layout from the 3.0.0 bundles. It starts up as usual
>>> and
>>> installs the features.xml I provide it for the test, but It
>>> turns out
>>> that none of the boot features are being activated, so SCR does
>>> not
>>> activate my components. Nor can I connect to the console to
>>> investigate
>>> further what's going on, because the shell/SSH are not active.
>>>
>>> The following messages are showing up in my karaf.log:
>>>
>>> INFO | Bundle org.apache.karaf.shell.__commands is waiting for
>>> namespace
>>> handlers
>>> INFO | Bundle org.apache.karaf.features.__command is waiting
>>> for
>>> namespace handlers
>>> INFO | Bundle org.apache.karaf.system.__command is waiting for
>>> namespace
>>> handlers
>>> INFO | Bundle org.apache.karaf.shell.help is waiting for
>>> dependencies
>>> [(objectClass=org.apache.__felix.service.threadio.__ThreadIO)]
>>> INFO | Bundle org.apache.karaf.bundle.__command is waiting for
>>> namespace
>>> handlers [http://karaf.apache.org/__xmlns/shell/v1.1.0
>>> <http://karaf.apache.org/xmlns/shell/v1.1.0>]
>>> INFO | Bundle org.apache.karaf.shell.console is waiting for
>>> dependencies
>>> [(objectClass=org.apache.__felix.service.command.__
>>> CommandProcessor),
>>> (objectClass=org.apache.felix.__service.threadio.ThreadIO)]
>>>
>>> Googling has linked this to machines without an internet
>>> connection,
>>> which is not the case here.
>>>
>>> My etc/org.apache.karaf.features.__cfg:
>>>
>>> featuresRepositories=mvn:org.__apache.karaf.features/__
>>> standard/3.0.0/xml/features,__mvn:org.apache.karaf.features/
>>> __enterprise/3.0.0/xml/features,__mvn:org.ops4j.pax.
>>> web/pax-web-__features/3.0.5/xml/features,__mvn:org.apache.
>>> karaf.features/__spring/3.0.0/xml/features
>>>
>>> featuresBoot=config,standard,__region,package,kar,ssh,__
>>> management,eventadmin,scr
>>>
>>> featuresBootAsynchronous=false
>>>
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org <ma...@apache.org>
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
Re: Boot features no longer starting after 3.0.0.RC1 -> 3.0.0 update
Posted by Ryan Moquin <fr...@gmail.com>.
You could set the log level to debug for you start it and see if it
mentions an artifact it can't retrieve.. not sure if it will, but worth a
try.
I also had the exact issue a few months ago.. can't remember what it was..
I thought I had asked about it on here... also, looks like you are
starting up asynchronously, I think to avoid problems you need to do it
synchronously...
Ryan
On Feb 10, 2014 7:25 AM, "Jean-Baptiste Onofré" <jb...@nanthrax.net> wrote:
> Hi
>
> - some boot features artifact are not present in the system repository
> (it's a bug and it will be fix in 3.0.1)
> - so, Karaf tries to download artifacts from internet, maybe your Karaf
> instance doesn't have access to Central ?
>
> Regards
> JB
>
> On 02/09/2014 11:44 PM, Jeremy Jongsma wrote:
>
>> Just the standard bundled ones I was using with RC1:
>>
>> featuresBoot=config,standard,region,package,kar,ssh,
>> management,eventadmin,scr
>>
>>
>> On Fri, Feb 7, 2014 at 4:51 PM, Jean-Baptiste Onofré <jb@nanthrax.net
>> <ma...@nanthrax.net>> wrote:
>>
>> Hi Jeremy,
>>
>> what's the kind of boot features do you have ? Especially in terms
>> of dependency to other features ?
>>
>> Regards
>> JB
>>
>>
>> On 02/07/2014 11:27 PM, Jeremy Jongsma wrote:
>>
>> Been scratching my head at this one all day: I just updated our
>> Karaf
>> version from 3.0.0.RC1 to 3.0.0 today, and all of our
>> integration tests
>> are failing due to boot features not installing. Has anything big
>> changed between RC1 and final that would affect boot feature
>> configuration? If I make no changes except setting the version
>> back to
>> 3.0.0.RC1, it works perfectly.
>>
>> During tests I use the maven karaf-assembly packaging goal to
>> build out
>> a Karaf app layout from the 3.0.0 bundles. It starts up as usual
>> and
>> installs the features.xml I provide it for the test, but It
>> turns out
>> that none of the boot features are being activated, so SCR does
>> not
>> activate my components. Nor can I connect to the console to
>> investigate
>> further what's going on, because the shell/SSH are not active.
>>
>> The following messages are showing up in my karaf.log:
>>
>> INFO | Bundle org.apache.karaf.shell.__commands is waiting for
>> namespace
>> handlers
>> INFO | Bundle org.apache.karaf.features.__command is waiting for
>> namespace handlers
>> INFO | Bundle org.apache.karaf.system.__command is waiting for
>> namespace
>> handlers
>> INFO | Bundle org.apache.karaf.shell.help is waiting for
>> dependencies
>> [(objectClass=org.apache.__felix.service.threadio.__ThreadIO)]
>> INFO | Bundle org.apache.karaf.bundle.__command is waiting for
>> namespace
>> handlers [http://karaf.apache.org/__xmlns/shell/v1.1.0
>> <http://karaf.apache.org/xmlns/shell/v1.1.0>]
>> INFO | Bundle org.apache.karaf.shell.console is waiting for
>> dependencies
>> [(objectClass=org.apache.__felix.service.command.__
>> CommandProcessor),
>> (objectClass=org.apache.felix.__service.threadio.ThreadIO)]
>>
>> Googling has linked this to machines without an internet
>> connection,
>> which is not the case here.
>>
>> My etc/org.apache.karaf.features.__cfg:
>>
>> featuresRepositories=mvn:org.__apache.karaf.features/__
>> standard/3.0.0/xml/features,__mvn:org.apache.karaf.features/
>> __enterprise/3.0.0/xml/features,__mvn:org.ops4j.pax.
>> web/pax-web-__features/3.0.5/xml/features,__mvn:org.apache.
>> karaf.features/__spring/3.0.0/xml/features
>>
>> featuresBoot=config,standard,__region,package,kar,ssh,__
>> management,eventadmin,scr
>>
>> featuresBootAsynchronous=false
>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org <ma...@apache.org>
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Boot features no longer starting after 3.0.0.RC1 -> 3.0.0 update
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
- some boot features artifact are not present in the system repository
(it's a bug and it will be fix in 3.0.1)
- so, Karaf tries to download artifacts from internet, maybe your Karaf
instance doesn't have access to Central ?
Regards
JB
On 02/09/2014 11:44 PM, Jeremy Jongsma wrote:
> Just the standard bundled ones I was using with RC1:
>
> featuresBoot=config,standard,region,package,kar,ssh,management,eventadmin,scr
>
>
> On Fri, Feb 7, 2014 at 4:51 PM, Jean-Baptiste Onofré <jb@nanthrax.net
> <ma...@nanthrax.net>> wrote:
>
> Hi Jeremy,
>
> what's the kind of boot features do you have ? Especially in terms
> of dependency to other features ?
>
> Regards
> JB
>
>
> On 02/07/2014 11:27 PM, Jeremy Jongsma wrote:
>
> Been scratching my head at this one all day: I just updated our
> Karaf
> version from 3.0.0.RC1 to 3.0.0 today, and all of our
> integration tests
> are failing due to boot features not installing. Has anything big
> changed between RC1 and final that would affect boot feature
> configuration? If I make no changes except setting the version
> back to
> 3.0.0.RC1, it works perfectly.
>
> During tests I use the maven karaf-assembly packaging goal to
> build out
> a Karaf app layout from the 3.0.0 bundles. It starts up as usual and
> installs the features.xml I provide it for the test, but It
> turns out
> that none of the boot features are being activated, so SCR does not
> activate my components. Nor can I connect to the console to
> investigate
> further what's going on, because the shell/SSH are not active.
>
> The following messages are showing up in my karaf.log:
>
> INFO | Bundle org.apache.karaf.shell.__commands is waiting for
> namespace
> handlers
> INFO | Bundle org.apache.karaf.features.__command is waiting for
> namespace handlers
> INFO | Bundle org.apache.karaf.system.__command is waiting for
> namespace
> handlers
> INFO | Bundle org.apache.karaf.shell.help is waiting for
> dependencies
> [(objectClass=org.apache.__felix.service.threadio.__ThreadIO)]
> INFO | Bundle org.apache.karaf.bundle.__command is waiting for
> namespace
> handlers [http://karaf.apache.org/__xmlns/shell/v1.1.0
> <http://karaf.apache.org/xmlns/shell/v1.1.0>]
> INFO | Bundle org.apache.karaf.shell.console is waiting for
> dependencies
> [(objectClass=org.apache.__felix.service.command.__CommandProcessor),
> (objectClass=org.apache.felix.__service.threadio.ThreadIO)]
>
> Googling has linked this to machines without an internet connection,
> which is not the case here.
>
> My etc/org.apache.karaf.features.__cfg:
>
> featuresRepositories=mvn:org.__apache.karaf.features/__standard/3.0.0/xml/features,__mvn:org.apache.karaf.features/__enterprise/3.0.0/xml/features,__mvn:org.ops4j.pax.web/pax-web-__features/3.0.5/xml/features,__mvn:org.apache.karaf.features/__spring/3.0.0/xml/features
>
> featuresBoot=config,standard,__region,package,kar,ssh,__management,eventadmin,scr
>
> featuresBootAsynchronous=false
>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Boot features no longer starting after 3.0.0.RC1 -> 3.0.0 update
Posted by Jeremy Jongsma <je...@barchart.com>.
Just the standard bundled ones I was using with RC1:
featuresBoot=config,standard,region,package,kar,ssh,
management,eventadmin,scr
On Fri, Feb 7, 2014 at 4:51 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> Hi Jeremy,
>
> what's the kind of boot features do you have ? Especially in terms of
> dependency to other features ?
>
> Regards
> JB
>
>
> On 02/07/2014 11:27 PM, Jeremy Jongsma wrote:
>
>> Been scratching my head at this one all day: I just updated our Karaf
>> version from 3.0.0.RC1 to 3.0.0 today, and all of our integration tests
>> are failing due to boot features not installing. Has anything big
>> changed between RC1 and final that would affect boot feature
>> configuration? If I make no changes except setting the version back to
>> 3.0.0.RC1, it works perfectly.
>>
>> During tests I use the maven karaf-assembly packaging goal to build out
>> a Karaf app layout from the 3.0.0 bundles. It starts up as usual and
>> installs the features.xml I provide it for the test, but It turns out
>> that none of the boot features are being activated, so SCR does not
>> activate my components. Nor can I connect to the console to investigate
>> further what's going on, because the shell/SSH are not active.
>>
>> The following messages are showing up in my karaf.log:
>>
>> INFO | Bundle org.apache.karaf.shell.commands is waiting for namespace
>> handlers
>> INFO | Bundle org.apache.karaf.features.command is waiting for
>> namespace handlers
>> INFO | Bundle org.apache.karaf.system.command is waiting for namespace
>> handlers
>> INFO | Bundle org.apache.karaf.shell.help is waiting for dependencies
>> [(objectClass=org.apache.felix.service.threadio.ThreadIO)]
>> INFO | Bundle org.apache.karaf.bundle.command is waiting for namespace
>> handlers [http://karaf.apache.org/xmlns/shell/v1.1.0]
>> INFO | Bundle org.apache.karaf.shell.console is waiting for
>> dependencies
>> [(objectClass=org.apache.felix.service.command.CommandProcessor),
>> (objectClass=org.apache.felix.service.threadio.ThreadIO)]
>>
>> Googling has linked this to machines without an internet connection,
>> which is not the case here.
>>
>> My etc/org.apache.karaf.features.cfg:
>>
>> featuresRepositories=mvn:org.apache.karaf.features/
>> standard/3.0.0/xml/features,mvn:org.apache.karaf.features/
>> enterprise/3.0.0/xml/features,mvn:org.ops4j.pax.web/pax-web-
>> features/3.0.5/xml/features,mvn:org.apache.karaf.features/
>> spring/3.0.0/xml/features
>>
>> featuresBoot=config,standard,region,package,kar,ssh,
>> management,eventadmin,scr
>>
>> featuresBootAsynchronous=false
>>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Boot features no longer starting after 3.0.0.RC1 -> 3.0.0 update
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Jeremy,
what's the kind of boot features do you have ? Especially in terms of
dependency to other features ?
Regards
JB
On 02/07/2014 11:27 PM, Jeremy Jongsma wrote:
> Been scratching my head at this one all day: I just updated our Karaf
> version from 3.0.0.RC1 to 3.0.0 today, and all of our integration tests
> are failing due to boot features not installing. Has anything big
> changed between RC1 and final that would affect boot feature
> configuration? If I make no changes except setting the version back to
> 3.0.0.RC1, it works perfectly.
>
> During tests I use the maven karaf-assembly packaging goal to build out
> a Karaf app layout from the 3.0.0 bundles. It starts up as usual and
> installs the features.xml I provide it for the test, but It turns out
> that none of the boot features are being activated, so SCR does not
> activate my components. Nor can I connect to the console to investigate
> further what's going on, because the shell/SSH are not active.
>
> The following messages are showing up in my karaf.log:
>
> INFO | Bundle org.apache.karaf.shell.commands is waiting for namespace
> handlers
> INFO | Bundle org.apache.karaf.features.command is waiting for
> namespace handlers
> INFO | Bundle org.apache.karaf.system.command is waiting for namespace
> handlers
> INFO | Bundle org.apache.karaf.shell.help is waiting for dependencies
> [(objectClass=org.apache.felix.service.threadio.ThreadIO)]
> INFO | Bundle org.apache.karaf.bundle.command is waiting for namespace
> handlers [http://karaf.apache.org/xmlns/shell/v1.1.0]
> INFO | Bundle org.apache.karaf.shell.console is waiting for
> dependencies
> [(objectClass=org.apache.felix.service.command.CommandProcessor),
> (objectClass=org.apache.felix.service.threadio.ThreadIO)]
>
> Googling has linked this to machines without an internet connection,
> which is not the case here.
>
> My etc/org.apache.karaf.features.cfg:
>
> featuresRepositories=mvn:org.apache.karaf.features/standard/3.0.0/xml/features,mvn:org.apache.karaf.features/enterprise/3.0.0/xml/features,mvn:org.ops4j.pax.web/pax-web-features/3.0.5/xml/features,mvn:org.apache.karaf.features/spring/3.0.0/xml/features
>
> featuresBoot=config,standard,region,package,kar,ssh,management,eventadmin,scr
>
> featuresBootAsynchronous=false
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com