Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5CA59200CB5 for ; Wed, 12 Jul 2017 14:59:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5B391168BD5; Wed, 12 Jul 2017 12:59:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A3348168BD2 for ; Wed, 12 Jul 2017 14:59:21 +0200 (CEST) Received: (qmail 35383 invoked by uid 500); 12 Jul 2017 12:59:20 -0000 Mailing-List: contact notifications-help@ofbiz.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ofbiz.apache.org Delivered-To: mailing list notifications@ofbiz.apache.org Received: (qmail 35374 invoked by uid 99); 12 Jul 2017 12:59:20 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jul 2017 12:59:20 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 426941960DA for ; Wed, 12 Jul 2017 12:59:20 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id rpn1vAEujd2t for ; Wed, 12 Jul 2017 12:59:18 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E88806287E for ; Wed, 12 Jul 2017 12:53:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5A4D5E0D92 for ; Wed, 12 Jul 2017 12:53:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2F43B24700 for ; Wed, 12 Jul 2017 12:53:00 +0000 (UTC) Date: Wed, 12 Jul 2017 12:53:00 +0000 (UTC) From: "Arun Patidar (JIRA)" To: notifications@ofbiz.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OFBIZ-9491) Deadlock on InventoryItem during load test MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 12 Jul 2017 12:59:22 -0000 [ https://issues.apache.org/jira/browse/OFBIZ-9491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083926#comment-16083926 ] Arun Patidar commented on OFBIZ-9491: ------------------------------------- Adding some more details. I am working on 14.12 code base but this case will be same on trunk as there is no change around InventoryItem update mechanism. Below are some inputs that can help us in research. - There is single InventoryItem record for a product with large number of qty. - Placing large number of orders for that product using script and quick ship it. (Goal is to place and fulfil more than 20k orders in a day) - Initially process runs successfully and after some time(hours) system started to show deadlock messages on console.(Refer attachment) > Deadlock on InventoryItem during load test > ------------------------------------------ > > Key: OFBIZ-9491 > URL: https://issues.apache.org/jira/browse/OFBIZ-9491 > Project: OFBiz > Issue Type: Improvement > Components: product > Affects Versions: Trunk > Reporter: Arun Patidar > Assignee: Arun Patidar > Attachments: OFBIZ-9491-console-logs.txt > > > I was trying to load test OFBiz with huge numbers of order creation and fulfilment. During test, I found a deadlock on InventoryItem enttiy. > Current system, invoke 'UpdateInventoryItemFromDetail' service to update InventoryItem QOH total and ATP total record. There is an Eca rule on create/update of InventoryItemDetail entity record which triggers service 'UpdateInventoryItemFromDetail'. So, with heavy load, InventoryItem record get lock and create deadlock condition. > I know that most of you are already aware with this issue. Please let me know if someone worked on it and have any idea to avoid this type of deadlock. -- This message was sent by Atlassian JIRA (v6.4.14#64029)