IBM Support

JR61071: THE ARTIFACT INDEXER USES A LOT OF MEMORY OR CPU AFTER A TRACK IS ARCHIVED

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

Direct links to fixes

8.6.0.201803-WS-BPM-IFJR61071
workflow.19002.delta.repository

 

APAR status

  • Closed as program error.

Error description

  • You might notice a lot of memory is being used, which might lead
to an OutofMemory issue in IBM Workflow Center immediately
after you archive a track.

You might also notice that the CPU usage is high, CPU starvation
detected messages appearing in the SystemOut.log file, and the
heapdump shows com.ibm.bpm.index.core.IArtifactRelationship
objects are using most of the memory in the JVM.

Local fix

  • Perform the following steps:
1. Before you archive tracks, turn off the Workflow Center
index. For more information, see "Configuring the Workflow
Center index"
(https://www.ibm.com/support/knowledgecenter/en/SS8JB4/com.ibm.w
bpm.admin.doc/topics/cconfigindex.html).
2. Archive the tracks.
3. Re-enable the Workflow Center index.

If you still experience high memory usage, rebuild the Workflow
Center index. For more information, see "Manually recreating or
updating the Workflow Center index"
(https://www.ibm.com/support/knowledgecenter/en/SS8JB4/com.ibm.w
bpm.admin.doc/topics/cupdatingindex.html).

Problem summary

  • The Artifact indexer tries to update its index with all newly
archived snapshots at the same time if a track is archived
during the index interval, requiring high memory or CPU usage.

PRODUCT AFFECTED
IBM Business Automation Workflow.

Problem conclusion

  • A fix that ensures the artifact indexer updates its index one
snapshot at a time when a track is archived and that the
artifact indexer has a capped limit to be indexed in one pass
reduce memory usage will be included in future release of
Business Automation Workflow.

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    JR61071
    • 

  • Reported component name
    BPM
    • 

  • Reported component ID
    5737A5700
    • 

  • Reported release
    I00
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2019-05-09
    • 

  • Closed date
    2019-06-07
    • 

  • Last modified date
    2019-06-07
    • 





    

  • 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
    BUS AUTO WORKFL
    • 

  • Fixed component ID
    5737H4100
    • 



Applicable component levels


    








      
              
                            

              

              [{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            07 June 2019
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback