[jboss-jira] [JBoss JIRA] (AS7-6106) Improper use of OperationContext.restartRequired() on 7.1 branch

[Stuart Douglas (JIRA)]

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

Stuart Douglas resolved AS7-6106.
---------------------------------

    Resolution: Out of Date

    
> Improper use of OperationContext.restartRequired() on 7.1 branch
> ----------------------------------------------------------------
>
>                 Key: AS7-6106
>                 URL: https://issues.jboss.org/browse/AS7-6106
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.1.3.Final (EAP)
>            Reporter: Ivo Studensky
>             Fix For: 7.1.4.Final (EAP)
>
>
> This actually is a subtask of AS7-6035 for additional changes in the 7.1 branch. In particular for two remaining occurrences of OperationContext.restartRequired() at:
> {noformat}
> org.jboss.as.logging.handlers.file.HandlerFileChange
> org.jboss.as.connector.subsystems.datasources.DataSourceDisable
> {noformat}
> Here is description of the original jira:
> {quote}
> Look or an fix uses of OperationContext.restartRequired() that should be using reloadRequired(). There are very few reasons why a full process restart should be needed for a configuration model change to take effect. Typically a full process restart would only be needed for a domain mode server whose JVM configuration settings have been changed in the host model.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira