Bug 793083 (JBEPP-165)

Summary:	disable pre-loading for JBossCachePersistenceManager
Product:	[JBoss] JBoss Enterprise Portal Platform 4	Reporter:	Gary Hu <garyhu2>
Component:	unspecified	Assignee:	Sohil Shah <sohil.shah>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3.0.GA_CP3	CC:	epp-bugs
Target Milestone:	---
Target Release:	4.3.0.GA_CP5
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-165
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-06-11 12:35:53 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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