<?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 Long running processes under deployment in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/long-running-processes-under-deployment/m-p/45058#M24984</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I was just wondering what happens to long running process under upgrade (upgrade of javaservice tasks, process definition etc) which results in restart of servlet container.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If the shutdown occurs in the middle of a service task then is there any way to re run it when the servlet container comes to live again ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there any way to track the processes which got affected of this scenario so that the processed don't get lost ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am just keen to find out what the best practices are to talke this kind of issue.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Sazzadul&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 03 Oct 2011 20:57:27 GMT</pubDate>
    <dc:creator>sazzadul</dc:creator>
    <dc:date>2011-10-03T20:57:27Z</dc:date>
    <item>
      <title>Long running processes under deployment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/long-running-processes-under-deployment/m-p/45058#M24984</link>
      <description>I was just wondering what happens to long running process under upgrade (upgrade of javaservice tasks, process definition etc) which results in restart of servlet container.If the shutdown occurs in the middle of a service task then is there any way to re run it when the servlet container comes to l</description>
      <pubDate>Mon, 03 Oct 2011 20:57:27 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/long-running-processes-under-deployment/m-p/45058#M24984</guid>
      <dc:creator>sazzadul</dc:creator>
      <dc:date>2011-10-03T20:57:27Z</dc:date>
    </item>
    <item>
      <title>Re: Long running processes under deployment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/long-running-processes-under-deployment/m-p/45059#M24985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;With long running processes deploying a new process definition will not change anything.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The long running process will just keep running in the old process definition.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;When you deploy a new version of a service task class, then that's effective immediately.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;When the server crashes during the execution of a service task, the process engine will execute that service task again when the process engine comes up again.&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>Tue, 04 Oct 2011 09:13:26 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/long-running-processes-under-deployment/m-p/45059#M24985</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2011-10-04T09:13:26Z</dc:date>
    </item>
    <item>
      <title>Re: Long running processes under deployment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/long-running-processes-under-deployment/m-p/45060#M24986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;When the server crashes during the execution of a service task, the process engine will execute that service task again when the process engine comes up again.&lt;/BLOCKQUOTE&gt;&lt;SPAN&gt;This does not happen automatically upon startup of the server right ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have to query the db([ACT_RU_EXECUTION]) and find out which service task didn't get completed and hence continue that service task by calling&lt;/SPAN&gt;&lt;BR /&gt;&lt;STRONG&gt;runtimeService.signal(id);&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;One problem with this approch is that there could be many web application(each containing a set of process definitions) using the same database thus upon startup querying ACT_RU_EXECUTION wont solve the problem since other web apps will have long running processes which reside in the same table. You get my point.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Wouldn't that have been just gorgeous if all these steps happened automatically or if there existed any api function which could be called upon startup of the server that took care of this for me ????&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Please verify if this is a real world problem scenrio and if so then suggest me of a solution.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Oct 2011 14:10:19 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/long-running-processes-under-deployment/m-p/45060#M24986</guid>
      <dc:creator>sazzadul</dc:creator>
      <dc:date>2011-10-19T14:10:19Z</dc:date>
    </item>
  </channel>
</rss>

