Bug 900076 (JBPAPP6-1523)

Summary:	Attribute passivate-events-on-replicate of cluster-passivation-store can't be change via drm or cli
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Ondrej Chaloupka <ochaloup>
Component:	EJB	Assignee:	Ivo Studensky <istudens>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0.0	CC:	cdewolf, istudens, ochaloup, rajesh.rajasekaran
Target Milestone:	---
Target Release:	EAP 6.4.0
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBPAPP6-1523
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-23 16:17:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ondrej Chaloupka 2012-03-21 13:44:30 UTC

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

Comment 1 Ondrej Chaloupka 2012-03-21 13:45:04 UTC

Link: Added: This issue Cloned from AS7-4246

Comment 6 Ondrej Chaloupka 2012-05-22 08:44:40 UTC

Assigning to Richard because of the original AS7 jira is assigned to him as well.

Comment 7 Anne-Louise Tangring 2012-11-13 21:01:40 UTC

Docs QE Status: Removed: NEW

Comment 8 JBoss JIRA Server 2013-02-25 17:51:50 UTC

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.

Comment 9 Ondrej Chaloupka 2013-02-26 15:51:51 UTC

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"}

Comment 10 JBoss JIRA Server 2013-02-26 16:32:07 UTC

Brian Stansberry <brian.stansberry> made a comment on jira AS7-4246

Thanks, Ondrej. That is definitely a bug.

Comment 11 Richard Achmatowicz 2013-09-12 10:08:51 UTC

FYI: pull request sent 
https://github.com/jbossas/jboss-eap/pull/395