[
https://issues.jboss.org/browse/AS7-4246?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-4246:
------------------------------------------
Same behaviour in 7.1.1 which leads me to believe that i'm not interpreting the issue
correctly.
Based on the above comment, it looks as though the configuration for the cache is being
changed correctly, but because there is no restart of the service being performed, the
cache instance held by the service is not picking it up. Checking.
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