<?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 Re: Deadlocks on multiserver configuration in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/deadlocks-on-multiserver-configuration/m-p/226741#M179871</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Sushant,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there a specific reason for not using a newer Activiti Engine version? We did improve job handling quite a bit in the latest releases. The first two questions I don't understand, maybe you can provide a bit more details for these. About the third question, we handle transactions on a database level with MyBatis. Every job is handled in a separate transaction and the transaction is committed when the engine has encountered a wait state in the process instance or the process instance has ended.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Dec 2015 11:03:08 GMT</pubDate>
    <dc:creator>trademak</dc:creator>
    <dc:date>2015-12-30T11:03:08Z</dc:date>
    <item>
      <title>Deadlocks on multiserver configuration</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/deadlocks-on-multiserver-configuration/m-p/226740#M179870</link>
      <description>Hi,We are currently facing a few deadlocks and some other exceptions when working in a highly concurrent environment.While analyzing the activiti code version. 5.16 I came across a few things which i didn't quite understand-1)In ExecuteJobsRunnable, JobExecutorContext is created for every thread, is</description>
      <pubDate>Wed, 30 Dec 2015 09:51:40 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/deadlocks-on-multiserver-configuration/m-p/226740#M179870</guid>
      <dc:creator>sushantmahajan</dc:creator>
      <dc:date>2015-12-30T09:51:40Z</dc:date>
    </item>
    <item>
      <title>Re: Deadlocks on multiserver configuration</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/deadlocks-on-multiserver-configuration/m-p/226741#M179871</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Sushant,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there a specific reason for not using a newer Activiti Engine version? We did improve job handling quite a bit in the latest releases. The first two questions I don't understand, maybe you can provide a bit more details for these. About the third question, we handle transactions on a database level with MyBatis. Every job is handled in a separate transaction and the transaction is committed when the engine has encountered a wait state in the process instance or the process instance has ended.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Dec 2015 11:03:08 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/deadlocks-on-multiserver-configuration/m-p/226741#M179871</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2015-12-30T11:03:08Z</dc:date>
    </item>
  </channel>
</rss>

