<?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: How to model a long-running java task? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/how-to-model-a-long-running-java-task/m-p/194018#M147148</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The default setting of the job executor is that it will start retrying a job if it's not completed within 5 minutes. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;So your solution to override that for your use case is perfectly fine. Another way to solve this is via the send/receive task solution you mentioned. This is described in this blogpost:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://bpmn20inaction.blogspot.nl/2012/12/implement-parallel-execution-in-activiti.html" rel="nofollow noopener noreferrer"&gt;http://bpmn20inaction.blogspot.nl/2012/12/implement-parallel-execution-in-activiti.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards, &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Jun 2014 19:17:17 GMT</pubDate>
    <dc:creator>trademak</dc:creator>
    <dc:date>2014-06-19T19:17:17Z</dc:date>
    <item>
      <title>How to model a long-running java task?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-to-model-a-long-running-java-task/m-p/194017#M147147</link>
      <description>I have a long running java task (runs longer than 5 minutes) that generates a ActivitiOptimisticLockingException because a 2nd instance of the process is started after 5 minutes – well before the 1st instance of the process has a chance to finish.This thread (http://forums.activiti.org/content/does-</description>
      <pubDate>Tue, 17 Jun 2014 21:34:03 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-to-model-a-long-running-java-task/m-p/194017#M147147</guid>
      <dc:creator>jvoris</dc:creator>
      <dc:date>2014-06-17T21:34:03Z</dc:date>
    </item>
    <item>
      <title>Re: How to model a long-running java task?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-to-model-a-long-running-java-task/m-p/194018#M147148</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The default setting of the job executor is that it will start retrying a job if it's not completed within 5 minutes. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;So your solution to override that for your use case is perfectly fine. Another way to solve this is via the send/receive task solution you mentioned. This is described in this blogpost:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://bpmn20inaction.blogspot.nl/2012/12/implement-parallel-execution-in-activiti.html" rel="nofollow noopener noreferrer"&gt;http://bpmn20inaction.blogspot.nl/2012/12/implement-parallel-execution-in-activiti.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards, &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2014 19:17:17 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-to-model-a-long-running-java-task/m-p/194018#M147148</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2014-06-19T19:17:17Z</dc:date>
    </item>
  </channel>
</rss>

