Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD8EB10C05 for ; Wed, 4 Dec 2013 01:12:36 +0000 (UTC) Received: (qmail 95234 invoked by uid 500); 4 Dec 2013 01:12:36 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 95197 invoked by uid 500); 4 Dec 2013 01:12:36 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 95144 invoked by uid 500); 4 Dec 2013 01:12:36 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 95032 invoked by uid 99); 4 Dec 2013 01:12:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Dec 2013 01:12:36 +0000 Date: Wed, 4 Dec 2013 01:12:36 +0000 (UTC) From: "Alena Prokharchyk (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-5358) API: synchronization on the object is broken MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Alena Prokharchyk created CLOUDSTACK-5358: --------------------------------------------- Summary: API: synchronization on the object is broken Key: CLOUDSTACK-5358 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5358 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Alena Prokharchyk Assignee: Kelven Yang Priority: Critical Fix For: 4.3.0 There is a way to synchronize API commands on certain CS object. For example, when createFirewallRule is called, synchronization on the Network is being done, so the next command won't be processed till the last one is executed. To enable it for the certain command, following methods have to be added to corresponding *Cmd class: @Override public String getSyncObjType() { return BaseAsyncCmd.networkSyncObject; } @Override public Long getSyncObjId() { return getIp().getAssociatedWithNetworkId(); } This logic got broken after the changes for vmSync got merged in. -- This message was sent by Atlassian JIRA (v6.1#6144)