[
https://issues.jboss.org/browse/AS7-4246?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on AS7-4246:
----------------------------------------------
Ondrej Chaloupka <ochaloup(a)redhat.com> made a comment on [bug
900076|https://bugzilla.redhat.com/show_bug.cgi?id=900076]
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"}
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
For more information on JIRA, see:
http://www.atlassian.com/software/jira