Bug 793083 (JBEPP-165) - disable pre-loading for JBossCachePersistenceManager
Summary: disable pre-loading for JBossCachePersistenceManager
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-165
Product: JBoss Enterprise Portal Platform 4
Classification: JBoss
Component: unspecified
Version: 4.3.0.GA_CP3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3.0.GA_CP5
Assignee: Sohil Shah
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-19 15:17 UTC by Gary Hu
Modified: 2012-02-28 16:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-11 12:35:53 UTC
Type: Task

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 793219 0 high CLOSED make disabling pre-loading by JBossCachePersistenceManager configurable 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBEPP-165 0 None None None Never

Internal Links: 793219

Description Gary Hu 2010-02-19 15:17:07 UTC 
Date of First Response: 2010-06-11 08:35:53
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=355234&gid=1354
project_key: JBEPP

There is request to disable the pre-loading for JBossCachePersistenceManager. This has been done in one of the branches. Please include it in the cp so that it's available in later release.
Comment 1 Gary Hu 2010-02-24 14:33:39 UTC 
If disabling the pre-loading, the server startup time will be decreased. However, the first hit to CMS resource will take longer time. 

It's more desirable if we could make it configurable so that the users can determine the best choice in their situations.
Comment 2 Martin Weiler 2010-04-23 07:54:06 UTC 
Link: Added: This issue related JBEPP-304
Comment 3 Sohil Shah 2010-06-11 12:35:53 UTC 
Now inside, cms.sar/META-INF/jboss-service.xml, pre-loading can be configured as shown below: Default is true

<PersistenceManager class="org.jboss.portal.cms.hibernate.state.JBossCachePersistenceManager">
                  <param name="schemaObjectPrefix" value="WSP"/>
                  <param name="JNDIName" value="java:/portal/cms/CMSSessionFactory"/>
                  <param name="externalBLOBs" value="false"/>
                  <!-- Change this value to configure the pre-loading. Default: true -->
                  <param name="enablePreLoading" value="true"/>
</PersistenceManager> 

It occurs twice in the configuration. Once for the workspace repository, and other for the version repository
Note You need to log in before you can comment on or make changes to this bug.