ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Patidar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-9491) Deadlock on InventoryItem during load test
Date Wed, 12 Jul 2017 12:53:00 GMT

    [ 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)

Mime
View raw message