You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Edell Nolan (JIRA)" <ji...@apache.org> on 2008/11/18 13:45:06 UTC

[jira] Created: (SMX4KNL-141) Kernel config edit command doesn't persist changes

Kernel config edit command doesn't persist changes
--------------------------------------------------

                 Key: SMX4KNL-141
                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-141
             Project: ServiceMix Kernel
          Issue Type: Bug
            Reporter: Edell Nolan
            Priority: Minor
             Fix For: 1.0.1


If you do the following 

servicemix config> edit org.ops4j.pax.logging
servicemix config> log4j.appender.out.file /tmp/servicemix.log
servicemix config> update

It does create my servicemix.log file in the /tmp directory and will log stuff there but if I shut the instance down 
and restart it - it redirects back to the original location for the servicemix.log file in the data directory.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SMX4KNL-141) Kernel config edit command doesn't persist changes

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/SMX4KNL-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47769#action_47769 ] 

Guillaume Nodet commented on SMX4KNL-141:
-----------------------------------------

Actually, this is the currently designed behavior.  Configuration updates do not take precedence over the configuration files.  So each time the configuration file is changed or reloaded due to a server restart, the changes done via the console are lost.
However, this may be improved by saving the changes to the properties file instead of saving the changes directly into the ConfigAdmin service.

> Kernel config edit command doesn't persist changes
> --------------------------------------------------
>
>                 Key: SMX4KNL-141
>                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-141
>             Project: ServiceMix Kernel
>          Issue Type: Bug
>            Reporter: Edell Nolan
>            Priority: Minor
>             Fix For: 1.0.1
>
>
> If you do the following 
> servicemix config> edit org.ops4j.pax.logging
> servicemix config> log4j.appender.out.file /tmp/servicemix.log
> servicemix config> update
> It does create my servicemix.log file in the /tmp directory and will log stuff there but if I shut the instance down 
> and restart it - it redirects back to the original location for the servicemix.log file in the data directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SMX4KNL-141) Kernel config edit command doesn't persist changes

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SMX4KNL-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated SMX4KNL-141:
------------------------------------

    Affects Version/s: 1.0.0
        Fix Version/s:     (was: 1.0.1)

> Kernel config edit command doesn't persist changes
> --------------------------------------------------
>
>                 Key: SMX4KNL-141
>                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-141
>             Project: ServiceMix Kernel
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Edell Nolan
>            Priority: Minor
>
> If you do the following 
> servicemix config> edit org.ops4j.pax.logging
> servicemix config> log4j.appender.out.file /tmp/servicemix.log
> servicemix config> update
> It does create my servicemix.log file in the /tmp directory and will log stuff there but if I shut the instance down 
> and restart it - it redirects back to the original location for the servicemix.log file in the data directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SMX4KNL-141) The config/edit command changes does not takes precedence over configuration files in the etc folder at restart

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SMX4KNL-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated SMX4KNL-141:
------------------------------------

    Summary: The config/edit command changes does not takes precedence over configuration files in the etc folder at restart  (was: Kernel config edit command doesn't persist changes)

> The config/edit command changes does not takes precedence over configuration files in the etc folder at restart
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: SMX4KNL-141
>                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-141
>             Project: ServiceMix Kernel
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Edell Nolan
>            Priority: Minor
>
> If you do the following 
> servicemix config> edit org.ops4j.pax.logging
> servicemix config> log4j.appender.out.file /tmp/servicemix.log
> servicemix config> update
> It does create my servicemix.log file in the /tmp directory and will log stuff there but if I shut the instance down 
> and restart it - it redirects back to the original location for the servicemix.log file in the data directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.