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 <[email protected]>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 <[email protected]>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 <[email protected]>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é" <[email protected]> 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é <[email protected]
>>>>> <mailto:[email protected]>> 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é
>>>>>     [email protected] <mailto:[email protected]>
>>>>>     http://blog.nanthrax.net
>>>>>     Talend - http://www.talend.com
>>>>>
>>>>>
>>>>>
>>>> --
>>>> Jean-Baptiste Onofré
>>>> [email protected]
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>
>>
>

Reply via email to