[jboss-jira] [JBoss JIRA] (WFCORE-548) Changing append on a file handler indicates a reload is required when it should be a runtime change

James Perkins (JIRA) issues at jboss.org
Thu Apr 9 20:20:18 EDT 2015


     [ https://issues.jboss.org/browse/WFCORE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins updated WFCORE-548:
---------------------------------
    Summary: Changing append on a file handler indicates a reload is required when it should be a runtime change  (was: Changing append on a file handler indicates a reload is required when a restart is required)


> Changing append on a file handler indicates a reload is required when it should be a runtime change
> ---------------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-548
>                 URL: https://issues.jboss.org/browse/WFCORE-548
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging
>            Reporter: James Perkins
>            Assignee: James Perkins
>
> Changing the {{append}} attribute at runtime results in the following output:
> {code}
> [standalone at localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=append,value=false)
> {
>     "outcome" => "success",
>     "response-headers" => {
>         "operation-requires-reload" => true,
>         "process-state" => "reload-required"
>     }
> }
> {code}
> A {{reload}} operation does not stop a file from being appended to. Either the behavior needs to change or the {{process-state}} should be "restart-required".
> The issue is likely the file name is checked during boot and hasn't changed therefore the it's not set which would cause the stream to the file to be closed and reopened without the append.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the jboss-jira mailing list