[ https://issues.jboss.org/browse/AS7-4246?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-4246: ------------------------------------------ I've checked 7.1.2.Final-SNAPSHOT for this issue and all looks to be OK. The subsystem is implemented using resources, the attribute definition for PASSIVATE_EVENTS_ON_REPLICATE specifies RESTART_NONE and the handler indicates that no restart is required after processing. Using the CLI, I found I was able to change the attribute value from its default to false: {noformat} [standalone@localhost:9999 /] /subsystem=ejb3/cluster-passivation-store=infinispan:read-attribute(name=passivate-events-on-replicate) { "outcome" => "success", "result" => true } [standalone@localhost:9999 /] /subsystem=ejb3/cluster-passivation-store=infinispan:write-attribute(name=passivate-events-on-replicate,value=false) {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=ejb3/cluster-passivation-store=infinispan:read-attribute(name=passivate-events-on-replicate) { "outcome" => "success", "result" => false } {noformat} There is also no reload required message appearing after operations indicating that a reload is required for the changes to take effect. I'll unzip a copy of 7.1.1 to see if I can reproduce the issue that Ondrej saw. -- 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

[ https://issues.jboss.org/browse/AS7-4246?page=com.atlassian.jira.plugin.s... ] Ondřej Chaloupka commented on AS7-4246: --------------------------------------- I've checked it once again and it seems to me that the behavior is what I've described. The cli console and the drm behaves in the same manner. They returned successfully performed operation but the results is not propagated to the app/test. When I set the attribute before starting server then it works fine. The passivation is not executed on replication. But when I set it by console or by drm after start of the server it does not have any affect on a running code. -- 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