DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21063>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21063 setAttribute does not work with no-cache option for dbpsml. Summary: setAttribute does not work with no-cache option for dbpsml. Product: Jetspeed Version: 1.4b4 Platform: Sun OS/Version: Solaris Status: NEW Severity: Critical Priority: Other Component: Portlet API AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] We have implemented a portal. Initially we found problems with psml caching, on load balanced servers. We have since turned caching off for db psml. Now, when we try to update attributes to the psml using AbstractPortlet.setAttribute(...), the psml in the database is updated. But, apparently, the psml(profile) in the rundata is not getting updated. So, any subsequent updates to the psml overwrite the previous update. This is only happening when psml caching is turned off. I dont understand the connection between the psml in the cache and that in the rundata. Here is an easy way to recreate this problem: Turn off db psml caching and start the portal engine. Minimize one of the portlets. After the page refreshes, minimize a different portlet. When the page refreshes again, you will see that the portlet minimized first will now be in normal state. I believe, we have solution to this issue (have succesfully verified the fix). But we are not 100% sure of the performance implications this might have on the system. I will send the patch, so that someone can verify the correctness of the fix. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
