[
https://issues.apache.org/jira/browse/OFBIZ-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283701#comment-14283701 ]
Jacopo Cappellato commented on OFBIZ-5065:
------------------------------------------
As far as I know the data stored in ProductCalculatedInfo is only used by the product search code of OFBiz.
In my opinion the long term solution to this problem would be that of replacing all the "product search" code (see the package org.ofbiz.product.product) with a search implementation based on modern search index technologies (e.g. Lucene/Solr).
With that said, if you do not need to sort your product search queries by totalQuantityOrdered, totalTimesViewed, averageCustomerRating then you can simply disable the ECA.
In the meantime we could actually convert this ECA into a batch process (a JobSandbox entry) that runs every x hours and computes the last x hours data and updates the ProductCalculatedInfo of all the products (being viewed, rated, ordered).
> ProductCalculatedInfo during storeOrder creates Deadlock
> --------------------------------------------------------
>
> Key: OFBIZ-5065
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5065> Project: OFBiz
> Issue Type: Bug
> Components: product
> Affects Versions: Release Branch 12.04
> Reporter: Markus M. May
> Priority: Minor
>
> We are experiencing problems with a deadlock on the ProductCalculatedInfo table in the storeOrder service.
> A possible solution seems to add require-new-transaction="true" to the countProductQuantityOrdered service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
