PK93666: MEMORY USAGE SPIKE WHILE PRE-RENDERING RESOURCES

6.1.0.3 Download: WebSphere Portal and WCM V6.1 fix pack 3, 6.1.5 feature pack
6.1.0.4 Download: WebSphere Portal and WCM V6.1.0 fix pack 4 & 6.1.5 fix pack 1
6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5
6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6
6.0.1.7 Download: WebSphere Portal and Web Content Manager V6.0.1, fix pack 7

APAR status

• Closed as program error.

Error description

• Near the end of the pre-rendering process, any required
  resources are saved to disk. It has been observed that the
  memory used by the WCM server increases steady  from this point
  till the end of the pre-rendering process where that memory is
  then released. This defect is to address that memory spike as it
  can lead to out of memory errors.
  
  During the resource pre-rendering process, the JCR node cache
  wasn't being periodically flushed and the progress was always
  keeping track of each resource that was pre-rendered which isn't
  required when not overwriting the existing pre-rendering
  directory.
  

Local fix

• The resource pre-rendering process was modified to periodically
  flush the JCR node cache as well as only keep track of
  pre-rendered resources when
  connect.moduleconfig.cacher.overwritecache is set to true.
  

Problem summary

• Memory usage spike while pre-rendering resources.
  Near the end of the pre-rendering process, any required
  resources are saved to disk. It has been observed that the
  memory used by the WCM server increases steady  from this point
  till the end of the pre-rendering process where that memory is
  then released. This defect is to address that memory spike as it
  can lead to out of memory errors.
  During the resource pre-rendering process, the JCR node cache
  wasn't being periodically flushed and the progress was always
  keeping track of each resource that was pre-rendered which isn't
  required when not overwriting the existing pre-rendering
  directory.
  

Problem conclusion

• The resource pre-rendering process was modified to periodically
  flush the JCR node cache as well as only keep track of
  pre-rendered resources when
  connect.moduleconfig.cacher.overwritecache is set to true.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE PORTA

• Fixed component ID

  5724E7600

Applicable component levels

• R60H PSY

     UP