IBM Support

JR60604: PROCESS FEDERATION SERVER INDEXERS ARE REGISTERED AS DIFFERENT CONSUMERS FOR A SAME INDEX

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 link to fix

pfs.19001.delta.repository

 

APAR status

  • Closed as program error.

Error description

  • When IBM Process Federation Server starts for the first time at
least two indexers for the same federated database and a same
Elasticsearch index, a race condition might cause the creation
of two entries with the same CONSUMER_ID column value in tables
PFS_BPD_CHANGE_LOG_CONSUMER (for bpd indexers) or
PFS_BPEL_CHANGE_LOG_CONSUMER (for bpel indexers). As a result,
the indexing process may slow down and issues might occur when
Process Federation Server runs its maintenance operations.

PRODUCTS AFFECTED
IBM Business Process Manager (BPM)
IBM BPM Express
Business Automation Workflow

Local fix

  • 1. Stop the BPD or BPEL indexers for the corresponding indexes
in either of the following ways:
-Stopping the corresponding Process Federation Server servers.
-Updating all the Process Federation Server server.xml files to
comment out the indexers.

2. Wait until the indexers are stopped. See the logging messages
in the servers consoles log files for confirmation.

3. Update the PFS_BPD_CHANGE_LOG_CONSUMER (for BPD) or
PFS_BPEL_CHANGE_LOG_CONSUMER (for BPEL) table so that only one
rows refers to each index in the CONSUMER_ID column. For
example, if both CONSUMER_001 and CONSUMER_002 are assigned to
the same index for BPEL data, run the following SQL statement to
 fix the table:

UPDATE PFS_BPEL_CHANGE_LOG_CONSUMER SET CONSUMER_ID = NULL where
COLUMN_NAME == "CONSUMER_002"

4. Restart the indexers.

Problem summary

  • No additional information is available.

Problem conclusion

  • A fix that prevent the indexers from assigning more than one
consumer column to a same index will be available in a future
release of IBM Business Automation Workflow.

Temporary fix

  • Not applicable.

Comments

  • 



APAR Information




    

  • APAR number
    JR60604
    • 

  • Reported component name
    BPM STANDARD
    • 

  • Reported component ID
    5725C9500
    • 

  • Reported release
    857
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2019-01-28
    • 

  • Closed date
    2019-02-08
    • 

  • Last modified date
    2019-02-08
    • 





    

  • 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
    BPM STANDARD
    • 

  • Fixed component ID
    5725C9500
    • 



Applicable component levels


    








      
              
                            

              

              [{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"857","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            08 February 2019
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback