Bug 793230 (JBEPP-315) - Cluster with 2-nodes: replication of portlet render parameters is not working
Summary: Cluster with 2-nodes: replication of portlet render parameters is not working
Keywords:
Status: CLOSED DEFERRED
Alias: JBEPP-315
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: unspecified
Version: 5.0.0.ER04
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-19 13:00 UTC by mposolda
Modified: 2012-01-06 11:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-315 0 None None None Never

Description mposolda 2010-04-19 13:00:45 UTC
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.

Comment 1 mposolda 2010-04-19 13:02:30 UTC
Link: Added: This issue is related to GTNPORTAL-853


Comment 2 mposolda 2010-04-19 13:03:49 UTC
Linked with GTNPORTAL-853, which is similar problem. Both of them are related to navigation state replication.

Comment 4 Prabhat Jha 2010-10-26 14:45:18 UTC
Thomas, pls comment on this based on what you decide.

Comment 5 Thomas Heute 2010-10-26 14:58:11 UTC
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)

Comment 7 Jared MORGAN 2011-11-17 23:45:07 UTC
Release Notes Docs Status: Added: Not Required



Note You need to log in before you can comment on or make changes to this bug.