<?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: 5.9 and exclusive jobs in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/5-9-and-exclusive-jobs/m-p/99246#M68567</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Long running service tasks are always a problem: since delegates are invoked synchronously, the transaction will be keept open for the time you work. If you take a long time to finish the work you will either run into transaction timeouts or lock the underlying resource (db) for too long.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Also keep in mind that the job executor has a max lock time after which it will assume that a job has failed.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 09 Mar 2012 12:51:43 GMT</pubDate>
    <dc:creator>meyerd</dc:creator>
    <dc:date>2012-03-09T12:51:43Z</dc:date>
    <item>
      <title>5.9 and exclusive jobs</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/5-9-and-exclusive-jobs/m-p/99244#M68565</link>
      <description>Hi,Just wanted to share this observation, maybe other people have the same opinion. The doc says about exclusive jobs:It is actually not a performance issue. Performance is an issue under heavy load. Heavy load means that all worker threads of the job executor are busy all the time.I wanted to get a</description>
      <pubDate>Fri, 09 Mar 2012 12:24:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/5-9-and-exclusive-jobs/m-p/99244#M68565</guid>
      <dc:creator>heymjo</dc:creator>
      <dc:date>2012-03-09T12:24:18Z</dc:date>
    </item>
    <item>
      <title>Re: 5.9 and exclusive jobs</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/5-9-and-exclusive-jobs/m-p/99245#M68566</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Consider:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- If you only have a single process instance in db: Since activiti enforces sequential execution of the process instance, the instance itself runs longer than if tasks from the instance would be executed concurrently.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- If you have multiple process instances: each thread of the job executor will execute a single instance. You will still do work concurrently but from different instances.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Mar 2012 12:43:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/5-9-and-exclusive-jobs/m-p/99245#M68566</guid>
      <dc:creator>meyerd</dc:creator>
      <dc:date>2012-03-09T12:43:23Z</dc:date>
    </item>
    <item>
      <title>Re: 5.9 and exclusive jobs</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/5-9-and-exclusive-jobs/m-p/99246#M68567</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Long running service tasks are always a problem: since delegates are invoked synchronously, the transaction will be keept open for the time you work. If you take a long time to finish the work you will either run into transaction timeouts or lock the underlying resource (db) for too long.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Also keep in mind that the job executor has a max lock time after which it will assume that a job has failed.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Mar 2012 12:51:43 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/5-9-and-exclusive-jobs/m-p/99246#M68567</guid>
      <dc:creator>meyerd</dc:creator>
      <dc:date>2012-03-09T12:51:43Z</dc:date>
    </item>
  </channel>
</rss>

