Red Hat Bugzilla – Bug 900378
CDI beans with SET replication trigger are not replicating
Last modified: 2015-05-28 05:26:25 EDT
Affects: Release Notes Workaround: Workaround Exists Workaround Description: Use SET_AND_NON_PRIMITIVE_GET replication trigger (the default). project_key: JBPAPP6 Please check if the use case is correct: https://github.com/rhusar/clusterbench/blob/master/clusterbench-ee6-web/src/main/java/org/jboss/test/clusterbench/web/cdi/CdiServlet.java https://github.com/rhusar/clusterbench/blob/master/clusterbench-ee6-web/src/main/java/org/jboss/test/clusterbench/web/cdi/SessionScopedCdiSerialBean.java The methods are only called on the CDI-mananged bean, there is no interaction with the HTTP session itself. Should the replication trigger on the bean itself or is anything else required? https://hudson.qa.jboss.com/hudson/job/eap-6x-failover-http-cdi-shutdown-repl-sync/2/
Link: Added: This issue Cloned from AS7-4726
Workflow: Removed: GIT Pull Request workflow Added: jira Security: Added: Public Docs QE Status: Added: NEW
Labels: Removed: eap6_need_triage Added: eap6_clustering eap6_need_triage
Release Notes Docs Status: Added: Not Yet Documented
Link: Added: This issue is a dependency of JBPAPP-9290
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue Release Notes Text: Added: Due to a bug in the Weld component, the <code>setAttribute</code> method is not called correctly. This causes CDI beans with the <code>SET</code> replication trigger to fail to be replicated. The workaround is to use the <code>SET_AND_NON_PRIMITIVE_GET</code> trigger for these beans. This will be fixed in a future release. Affects: Added: Release Notes
Labels: Removed: eap6_clustering eap6_need_triage Added: eap601candidate eap6_clustering
Added workaround. Defer to EAP 6.1.
Workaround Description: Added: Use SET_AND_NON_PRIMITIVE_GET replication trigger (the default). Workaround: Added: Workaround Exists
Writer: Added: mistysj
Release Notes Text: Removed: Due to a bug in the Weld component, the <code>setAttribute</code> method is not called correctly. This causes CDI beans with the <code>SET</code> replication trigger to fail to be replicated. The workaround is to use the <code>SET_AND_NON_PRIMITIVE_GET</code> trigger for these beans. This will be fixed in a future release. Added: Due to a bug in the Weld component, the `setAttribute` method is not called correctly. This causes CDI beans with the `SET` replication trigger to fail to be replicated. The workaround is to use the `SET_AND_NON_PRIMITIVE_GET` trigger for these beans. This will be fixed in a future release.
Release Notes Docs Status: Removed: Documented as Known Issue Writer: Removed: mistysj Release Notes Text: Removed: Due to a bug in the Weld component, the `setAttribute` method is not called correctly. This causes CDI beans with the `SET` replication trigger to fail to be replicated. The workaround is to use the `SET_AND_NON_PRIMITIVE_GET` trigger for these beans. This will be fixed in a future release. Docs QE Status: Removed: NEW
This will be addressed by new web session clustering implementation scheduled for 6.3.
I'm lowering the priority of this issue. The SET replication trigger should only be used with care - so much that it won't exist in EAP7. Nor is this the default behavior.
Setting target release to EAP7. replication-trigger will be removed in this release.
Moving to documentation component: it should be permanently documented (as a note/warning/or so) that using Weld/CDI and having replication-trigger configured to SET is not supported in EAP 6.x releases.
*** Bug 1150079 has been marked as a duplicate of this bug. ***