[ 
https://jira.nuxeo.com/browse/NXP-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=100203#comment-100203
 ] 

Florent Guillaume edited comment on NXP-7356 at 8/12/11 2:06 PM:
-----------------------------------------------------------------

Added control of non hierarchy fragments delete using the system property 
{{nuxeo.vcs.isAllowedDeleteNonHierarchyFragments}}. Will be integrated in a 
more convenient way later, once we will be sure about this fix.

      was (Author: slacoin):
    Added control of non hierarchy fragments delete using the system property 
{{nuxeo.vcs.nuxeo.vcs.isAllowedDeleteNonHierarchyFragments}}. Will be 
integrated in a more convenient way later, once we will be sure about this fix.
  
> transaction deadlocks while updating documents wlth a SQL server backend
> ------------------------------------------------------------------------
>
>                 Key: NXP-7356
>                 URL: https://jira.nuxeo.com/browse/NXP-7356
>             Project: Nuxeo Enterprise Platform
>          Issue Type: Bug
>          Components: Core SQL Storage
>    Affects Versions: 5.4.1
>            Reporter: Stéphane Lacoin
>            Priority: Critical
>             Fix For: 5.4.3
>
>
> In scenari, when we're importing documents in parallel, we've got errors from 
> the database :
> {code}
> Caused by: org.nuxeo.ecm.core.api.WrappedException: Exception: 
> java.sql.BatchUpdateException. message: Transaction (Process ID 65) was 
> deadlocked on lock resources with another proc\
> ess and has been chosen as the deadlock victim. Rerun the transaction.
> {code}
> Each import is rooted in a distinct folder. So the database alters should not 
> conflicts. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets

Reply via email to