Bug 792994 (JBEPP-74) - Preferences values are not getting replicated in clustered setup
Summary: Preferences values are not getting replicated in clustered setup
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-74
Product: JBoss Enterprise Portal Platform 4
Classification: JBoss
Component: Portal
Version: 4.3.0.GA,4.3.0.GA_CP1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3.0.GA_CP2
Assignee: Thomas Heute
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-07 10:17 UTC by Martin Weiler
Modified: 2012-02-28 16:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
EPP 4.3, two clustered instances, shared database
Last Closed: 2009-07-22 07:25:42 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


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

Description Martin Weiler 2009-05-07 10:17:20 UTC 
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/293343
project_key: JBEPP

Any change in portlet preferences on one of the servers (using Admin Portal) is not getting reflected on the other cluster nodes. 

Steps to replicate this is:
1. Develop a portlet with some preferences
2. Deploy the portlet war on 2 nodes running under cluster.
3. Use SERVER1 to change the preference value
4. Hit SERVER1 to see that portlet and preferences value printed on stdout.
5. Hit SERVER2 and verify the preferences. This will print old value.
6. Change the same preference on SERVER2 and see StaleStateException.
Comment 1 Martin Weiler 2009-05-07 10:18:10 UTC 
Link: Added: This issue depends JBPORTAL-2389
Note You need to log in before you can comment on or make changes to this bug.