Bug 837029

Summary: Change of JBC configuration - LRU algorithm + separate configuration for portal-system workspace
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: Michal Vanco <mvanco>
Component: PortalAssignee: Nobody <nobody>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.2.1.GACC: epp-bugs, mvecera, theute
Target Milestone: ---   
Target Release: 5.2.2.ER01   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
A change made to the JBoss Cache cache algorithm caused performance issues for some configuration scenarios. The fix introduces configuration with an improved algorithm. The new algorithm references a new configuration file, which now loads correctly. This corrects the performance issues.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:20:15 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:
Embargoed:
Attachments:
Description Flags
Patch with new JBC configuration none

Description Michal Vanco 2012-07-02 14:45:51 UTC 
Created attachment 595752 [details]
Patch with new JBC configuration

This BZ is based on https://bugzilla.redhat.com/show_bug.cgi?id=808106 and communication at jbossexo ML.

Attached patch contains JBC configuration with LRU expiration algorithm and also separate configuration for portal-system workspace.
Comment 1 JBoss JIRA Server 2012-07-03 08:15:24 UTC 
Boleslaw Dawidowicz <boleslaw.dawidowicz> updated the status of jira GTNPORTAL-2489 to Resolved
Comment 2 Michal Vanco 2012-07-13 09:43:30 UTC 
New configuration file is used & loaded properly.
Comment 3 hfnukal@redhat.com 2012-08-27 14:28:25 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: Change of cache algorithm
Consequences: Performance issues for some scenarioas
Fix: New configuration with different algorithm
Result: New configuration file is used & loaded properly
Comment 4 Jared MORGAN 2012-08-27 23:18:46 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1 @@
-Cause: Change of cache algorithm
+A change made to the JBoss Cache cache algorithm caused performance issues for some configuration scenarios. The fix introduces configuration with an improved algorithm. The new algorithm references a new configuration file, which now loads correctly. This corrects the performance issues.-Consequences: Performance issues for some scenarioas
-Fix: New configuration with different algorithm
-Result: New configuration file is used & loaded properly
Comment 5 Viliam Rockai 2012-08-28 11:25:56 UTC 
Verified again at 5.2.2 CR01
Comment 9 Red Hat Bugzilla 2025-02-10 03:20:15 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.