<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Constant deadlock with Oracle in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/constant-deadlock-with-oracle/m-p/248465#M201595</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We have an application that uses Alfresco Web Service CMIS API. At first we did not have many problems but currently every other day the production system's Alfresco stops working (does not check in documents, does not retrieve documents, etc) when we check the log we have a recurrent problem with deadlocks. It is the only error in the log. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I've tried to find information in the forum but all the posts related to deadlocks that I've found do not apply here.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Can anyone throw a little bit of light?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The application is using Alfresco 3.2.0 r2 (2440). We have a known problem that the frontend accepts several name characters that are not accepted by Alfresco. After the document is uploaded to the server a process scheduled to run every few minutes sends the documents to a system and then uploads them to Alfresco. The process continues to upload the document with the invalid name until we find that an incorrect document name is used and manually correct it. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The most recent deadlock problem happened after trying to upload the document with the incorrect name repeatedly. This is the partial log &lt;/SPAN&gt;&lt;A href="http://pastebin.com/8YBXtW7w" rel="nofollow noopener noreferrer"&gt;http://pastebin.com/8YBXtW7w&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Right before Alfresco stopped working the log showed the line:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;21:33:22,323 WARN&amp;nbsp; [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;BR /&gt;&lt;SPAN&gt;After that we restarted Alfresco and deadlocks popped everywhere. Here is the log &lt;/SPAN&gt;&lt;A href="http://pastebin.com/5ZgzXtL6" rel="nofollow noopener noreferrer"&gt;http://pastebin.com/5ZgzXtL6&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Nov 2012 15:52:36 GMT</pubDate>
    <dc:creator>anxtr</dc:creator>
    <dc:date>2012-11-08T15:52:36Z</dc:date>
    <item>
      <title>Constant deadlock with Oracle</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/constant-deadlock-with-oracle/m-p/248465#M201595</link>
      <description>We have an application that uses Alfresco Web Service CMIS API. At first we did not have many problems but currently every other day the production system's Alfresco stops working (does not check in documents, does not retrieve documents, etc) when we check the log we have a recurrent problem with d</description>
      <pubDate>Thu, 08 Nov 2012 15:52:36 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/constant-deadlock-with-oracle/m-p/248465#M201595</guid>
      <dc:creator>anxtr</dc:creator>
      <dc:date>2012-11-08T15:52:36Z</dc:date>
    </item>
    <item>
      <title>Re: Constant deadlock with Oracle</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/constant-deadlock-with-oracle/m-p/248466#M201596</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;since I was similarily affected by this way back when one of our customers was still using 3.2.something, I know that there were a couple of indices missing in Oracle, which resulted in too many rows to be locked ending up in a deadlock. See &lt;/SPAN&gt;&lt;A href="https://issues.alfresco.com/jira/browse/ALF-5165" rel="nofollow noopener noreferrer"&gt;https://issues.alfresco.com/jira/browse/ALF-5165&lt;/A&gt;&lt;SPAN&gt; which is based on one of our ACTs at the time.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Consider upgrading to an up-to-date Alfresco release since 3.2 was quite a while ago and a lot of fixes have been included since then (e.g. another deadlock possibility &lt;/SPAN&gt;&lt;A href="https://issues.alfresco.com/jira/browse/ALF-5663" rel="nofollow noopener noreferrer"&gt;https://issues.alfresco.com/jira/browse/ALF-5663&lt;/A&gt;&lt;SPAN&gt;).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Nov 2012 16:43:02 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/constant-deadlock-with-oracle/m-p/248466#M201596</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2012-11-09T16:43:02Z</dc:date>
    </item>
  </channel>
</rss>

