Uploaded image for project: 'Application Controller'
  1. Application Controller
  2. APPC-1638

DeadLock in UPLOAD_CONFIG During Sync

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • El Alto Release
    • Dublin Release
    • APPC
    • None

      As an onap developer, I want to perform Sync LCM call in APPC and retrieve the running configuration from Node. This operation works well for one request however if we introduce multiple requests then APPC fails to update the UPLOAD_CONFIG table and ends with deadlock error.

       Exception in APPC logs:

      2019-07-16 11:53:00,842 | ERROR | ppc-dispatcher-9 | CachedDataSource                 | 203 - org.onap.ccsdk.sli.core.dblib-provider - 0.4.1 | <dbhost> failed to execute: INSERT INTO UPLOAD_CONFIG (request_id, originator_id, service_description, action, vnf_id, vnf_name, vm_name, vnf_type, vnfc_type, host_ip_address, config_indicator, content) SELECT request_id, originator_id, service_description, action, vnf_id, vnf_name, vm_name, vnf_type, vnfc_type, host_ip_address, 'Current', content FROM UPLOAD_CONFIG WHERE vnf_id ='33522854-d7bb-4fca-8102-b843ff64c608' AND config_indicator = 'Running' AND (pending_delete IS NULL OR pending_delete != 'Y')  with no arguments. 2019-07-16 11:53:00,842 | ERROR | ppc-dispatcher-9 | CachedDataSource                 | 203 - org.onap.ccsdk.sli.core.dblib-provider - 0.4.1 | <dbhost> failed to execute: INSERT INTO UPLOAD_CONFIG (request_id, originator_id, service_description, action, vnf_id, vnf_name, vm_name, vnf_type, vnfc_type, host_ip_address, config_indicator, content) SELECT request_id, originator_id, service_description, action, vnf_id, vnf_name, vm_name, vnf_type, vnfc_type, host_ip_address, 'Current', content FROM UPLOAD_CONFIG WHERE vnf_id ='33522854-d7bb-4fca-8102-b843ff64c608' AND config_indicator = 'Running' AND (pending_delete IS NULL OR pending_delete != 'Y')  with no arguments. java.sql.SQLTransactionRollbackException: (conn=537411) Deadlock found when trying to get lock; try restarting transaction 

            lathish lathish
            lathish lathish
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: