[jboss-jira] [JBoss JIRA] (AS7-3194) Improper handling of load metric add/remove in mod_cluster subsystem

Jean-Frederic Clere (JIRA) jira-events at lists.jboss.org
Wed Jan 25 05:10:18 EST 2012


    [ https://issues.jboss.org/browse/AS7-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661704#comment-12661704 ] 

Jean-Frederic Clere commented on AS7-3194:
------------------------------------------

1) is easy.
2) I have to check how context.reloadRequired() interacts with mod_cluster.
                
> Improper handling of load metric add/remove in mod_cluster subsystem
> --------------------------------------------------------------------
>
>                 Key: AS7-3194
>                 URL: https://issues.jboss.org/browse/AS7-3194
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering, Domain Management, Web
>    Affects Versions: 7.1.0.CR1b
>            Reporter: Brian Stansberry
>            Assignee: Jean-Frederic Clere
>             Fix For: 7.1.0.Final
>
>
> The ModClusterAddMetric and ModClusterAddCustomMetric handlers have two problems:
> 1) They only run if (context.getType() == OperationContext.Type.SERVER)
> This means a client updating the subsystem config on a domain controller will not be able to have the change reflected in the domain wide model (and it won't be persisted to domain.xml)
> 2) If they are run on the server, they don't modify the runtime or call context.reloadRequired(). So the runtime services are out of sync with the configuration but the server state doesn't reflect that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list