project_key: JBPAPP6 Setting attribute passivate-events-on-replicate via drm or cli does not take affect until operation :reload is used. In case that the attribute ( <cluster-passivation-store name="infinispan" cache-container="ejb" passivate-events-on-replicate="false" />) is set directly in standalone*.xml configuration file the supposed functionality is working. The test for this could be checked on: https://github.com/ochaloup/jboss-as/blob/JBQA-5855-test-migration-passivation-in-cluster/testsuite/integration/clust/src/test/java/org/jboss/as/test/clustering/cluster/ejb3/stateful/passivation/ClusterPassivationTestCase.java
Link: Added: This issue Cloned from AS7-4246
Assigning to Richard because of the original AS7 jira is assigned to him as well.
Docs QE Status: Removed: NEW
Brian Stansberry <brian.stansberry> made a comment on jira AS7-4246 Please explain how this is a bug. It is not a requirement that the change be immediately propagated to the running services without an intermediate reload.
Hi, you're right. The bug was not created correctly. The only problem is that user is not informed that the reload is required. No info about necessary reload here. [standalone@localhost:9999 /] /subsystem=ejb3/cluster-passivation-store=infinispan:write-attribute(name=passivate-events-on-replicate, value=true) {"outcome" => "success"}
Brian Stansberry <brian.stansberry> made a comment on jira AS7-4246 Thanks, Ondrej. That is definitely a bug.
FYI: pull request sent https://github.com/jbossas/jboss-eap/pull/395