PK83629: WORKSPACE CACHE CLEARING DOESN'T ALWAYS OCCUR, IF WE ONLY HAVE SYSTEM CREDENTIALS.

APAR status

• Closed as program error.

Error description

• Java Heap OutOfMemory while running WCM MemberFixer tool.
  Heapdump analysis shows the StrongWorkSpaceState objects are not
  being cleared. WorkSpace cache clearing does not always
  occur.
  
  
  
  758,166,104 (40%) [24] 2
  com/ibm/workplace/wcm/services/repository/WorkspaceManager$Works
  paceCont
  ainer 0x7572e240
   758,166,080 (40%) [48] 1 java/util/HashMap 0x7572e210
    758,166,032 (40%) [80] 1 array of java/util/HashMap$Entry
  0x7572e1c0
     758,165,952 (40%) [32] 2 java/util/HashMap$Entry 0x7598a958
      758,165,920 (40%) [96] 11 com/ibm/icm/jcr/WorkspaceImpl
  0x75a197d8
       758,164,704 (40%) [48] 5
  com/ibm/icm/jcr/StrongWorkspaceState
  0x7598e640
        754,979,408 (40%) [48] 1 java/util/HashMap 0x7598e5a8
         754,979,360 (40%) [524,304] 61,414 array of
  java/util/HashMap$Entry 0xb5c29aa0
          93,168 (0%) [32] 3 java/util/HashMap$Entry 0xb28f1180
           72,224 (0%) [32] 3 java/util/HashMap$Entry 0xb28eabc8
            52,128 (0%) [32] 3 java/util/HashMap$Entry 0xb0f3d3b8
            19,952 (0%) [184] 11 com/ibm/icm/jcr/NodeImpl
  0xb28eadf8
            112 (0%) [32] 1 java/lang/String 0x64704748
           20,800 (0%) [184] 11 com/ibm/icm/jcr/NodeImpl
  0xb28f13b0
           112 (0%) [32] 1 java/lang/String 0x648ae468
          88,216 (0%) [32] 3 java/util/HashMap$Entry 0x7b530a78
          80,320 (0%) [32] 3 java/util/HashMap$Entry 0xb32f9e78
  

Local fix

Problem summary

• Problem Summary:
   Out of memory error occurs when running the MemberFixer Module.
  
  Detailed Problem Description:
   The customer repeatedly sees the failure of the MemberFixer
  Module run due to java.lang.OutOfMemoryError errors. This occurs
   regardless of the numberOfJcrOperationsPerLogin specified in
  the url, which is supposed to clear the workspace caches
   every number of JCR operations specified.
  

Problem conclusion

• Problem Analysis:
   It was found that the functionality to clear the caches had an
  incorrect checking that results in the system workspaces not
  being cleared.
  
  Problem Solution:
          The checking has been corrected and all workspaces are
  being cleared per the numberOfJcrOperationsPerLogin parameter.
  

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

  LOTUS WEB CONT

• Fixed component ID

  5724I2900

Applicable component levels

• R60G PSY

     UP