servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SMX4KNL-141) Kernel config edit command doesn't persist changes
Date Mon, 01 Dec 2008 20:34:05 GMT

    [ 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.


Mime
View raw message