karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grzegorz Grzybek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-955) Confusing behavior of ConfigAdmin
Date Tue, 11 Oct 2016 08:43:20 GMT

    [ https://issues.apache.org/jira/browse/KARAF-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564918#comment-15564918

Grzegorz Grzybek commented on KARAF-955:

Yes, it is. It's happening anyway, but {{etc/}} _belongs_ to fileinstall component. And fileinstall
reads the data, compares if anything has changed and updates configadmin configurations then.
In the meantime, configadmin component does its job as well - serving/providing configuration
data to other components.

In OSGi many things happen in parallel. You, by very nature of OSGi, can't _shape_ each quantum
moment of the framework. You rather tell the framework to transition into different state.

> Confusing behavior of ConfigAdmin
> ---------------------------------
>                 Key: KARAF-955
>                 URL: https://issues.apache.org/jira/browse/KARAF-955
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-config
>    Affects Versions: 2.2.4
>            Reporter: Sergey Zhemzhitsky
> Hi there,
> I've faced with the following behavior of ConfigAdmin which I suppose is a little bit
> Steps to reproduce:
> # Start Karaf
> # Go to *$\{karaf.home}/data/log* directory
> # *karaf.log* file should be there
> # Stop Karaf
> # Go to *$\{karaf.home}/data/log* directory and delete *karaf.log* file
> # When Karaf is stopped change *log4j.appender.out.file* property in the *$\{karaf.home}/etc/org.ops4j.pax.logging.cfg*
file from *$\{karaf.data}/log/karaf.log* to *$\{karaf.data}/log/karaf1.log*
> # Start Karaf
> # Go to *$\{karaf.home}/data/log* directory
> # Only *karaf1.log* file is expected to be there, but empty *karaf.log* that has been
deleted on the step 4 is also there.

This message was sent by Atlassian JIRA

View raw message