Versions Compared

Old Version 8

changes.mady.by.user Former user

Saved on

compared with

New Version 9

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sample Heap Dump Analysis Dominator Tree

OccurenceThis occurs when WSO2 DAS receives a large bulk of data to be indexed.
Possible Reasons

The indexing operation of the bulk of data handled maybe using almost all the available memory based on the taxanomy cache size specified in the <DAS_HOME>/repository/conf/analytics/analytics-config.xml file.

e.g., If the available memory is 3.6 GB and 2.9 GB of that is used by the indexing operation as shown in the sample given above.
Image Added 

Recommended Action

To overcome this out of memory issue, increase the taxonomy cache size by following the procedure given below.

  1. Install the latest WUM update.

  2. Add the following configuration under analytics-dataservice-configuration in the <DAS_HOME>/repository/conf/analytics/analytics-config.xml file (if it does not already exist).

    Info

    When ths configuration is not added in the analytics-config.xml file, the default values shown below apply.

    Code Block
    languagexml
    <taxonomy-writer-cache>
     <cacheType>DEFAULT</cacheType>
     <!--<LRUType>STRING</LRUType>-->
     <!--<cacheSize>4096</cacheSize>-->
</taxonomy-writer-cache>

  3. To save the large taxanomy indexes in the file system of DAS instead of in the memory, change the value of the cacheType parameter to LRU as shown below.
    <cacheType>LRU</cacheType>

    Info

    When the value specified for the cacheType parameter is DEFAULT, taxanomy indexes are saved in the DAS memory.

  4. Uncomment the LRUType parameter.
  5. Uncomment the cacheSize parameter. Then increase the value for this parameter as required.
  6. Restart the server.

...