| Summary: | Cluster with 2-nodes: replication of portlet render parameters is not working | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | mposolda |
| Component: | unspecified | Assignee: | Default User <jbpapp-maint> |
| Status: | CLOSED DEFERRED | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.0.ER04 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-315 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
EPP5 CR1 SNAPSHOT 100414 - 2-nodes cluster,
Loadbalancer: Apache 2.0.52, mod_jk 1.2.28, sticky_session enabled,
Sun JDK 1.6
|
|
| Last Closed: | 2012-01-06 11:36:13 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: | |
Link: Added: This issue is related to GTNPORTAL-853 Linked with GTNPORTAL-853, which is similar problem. Both of them are related to navigation state replication. Thomas, pls comment on this based on what you decide. I prefer to not impact the performances and to not implement this. Unless we find a real world scenario where this would be critical (Keeping UI state at all cost is not desirable for most educated users I talked too) Release Notes Docs Status: Added: Not Required |
project_key: JBEPP I did some failover testing of inter-portlet communication and replication of render parameters in JSR-286 portlets. Render parameters should be available within more HTTP requests and so they should be replicated, otherwise client is able to recognize the change if failover happens. Current state is, that replication of render parameters does not work right now. Especially I tested this scenario: a) Start of 2 nodes with EPP5, 1 node with apache loadbalancer b) Trigger some action in JSR-286 portlet and use actionResponse.setRenderParameter("myParam", "myValue"); " in processAction method. Render parameter is correctly read in method "render" c) Refresh the page in browser to force another HTTP request without action phase now. Render parameter can still be read in method "render" (render parameters are alive within more HTTP requests). d) Doing failover of node1 e) Refresh the page again. Now the render parameter is lost and can't be seen on node2. I verified with normal render parameters and also with public render parameters. But replication is not working for both of them.