[jboss-jira] [JBoss JIRA] (AS7-4246) Attribute passivate-events-on-replicate of cluster-passivation-store can't be change via drm or cli
[
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.
Attribute passivate-events-on-replicate of cluster-passivation-store
can't be change via drm or cli
---------------------------------------------------------------------------------------------------
Key: AS7-4246
URL: https://issues.jboss.org/browse/AS7-4246
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.1.Final
Reporter: Ondřej Chaloupka
Assignee: Richard Achmatowicz
Labels: eap6_need_triage
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-passiv...
--
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