<?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: updating activiti in a clustered environment in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/updating-activiti-in-a-clustered-environment/m-p/225103#M178233</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;DB will block update if something is going on for changing objects. In worst case it can produce inconsistent DB. It's also possible high load on processes/DB will postpone update infinitely.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If update is done and something vital is changed, "old" cluster nodes will stop working normally up to restart.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I tried update in 2 nodes cluster from activiti 5.19 to activiti 5.20. I worked, but not smoothly. Both nodes tried to make update of DB and after all I had to restart them again.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;IMHO you should shut down every node, upgrade/start one node to make DB update and only then then update/start other nodes.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Aug 2016 10:30:32 GMT</pubDate>
    <dc:creator>warper</dc:creator>
    <dc:date>2016-08-26T10:30:32Z</dc:date>
    <item>
      <title>updating activiti in a clustered environment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/updating-activiti-in-a-clustered-environment/m-p/225102#M178232</link>
      <description>Hi,I have a question regarding the update behavior of the db schema in activiti. I think I understood how the mechanism works in principle: you can specify the property 'databaseSchemaUpdate' and set it to 'true'. On the next startup of the ProcessEngine, this will execute the necessary db operation</description>
      <pubDate>Thu, 25 Aug 2016 14:39:15 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/updating-activiti-in-a-clustered-environment/m-p/225102#M178232</guid>
      <dc:creator>stefanhenke</dc:creator>
      <dc:date>2016-08-25T14:39:15Z</dc:date>
    </item>
    <item>
      <title>Re: updating activiti in a clustered environment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/updating-activiti-in-a-clustered-environment/m-p/225103#M178233</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;DB will block update if something is going on for changing objects. In worst case it can produce inconsistent DB. It's also possible high load on processes/DB will postpone update infinitely.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If update is done and something vital is changed, "old" cluster nodes will stop working normally up to restart.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I tried update in 2 nodes cluster from activiti 5.19 to activiti 5.20. I worked, but not smoothly. Both nodes tried to make update of DB and after all I had to restart them again.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;IMHO you should shut down every node, upgrade/start one node to make DB update and only then then update/start other nodes.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Aug 2016 10:30:32 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/updating-activiti-in-a-clustered-environment/m-p/225103#M178233</guid>
      <dc:creator>warper</dc:creator>
      <dc:date>2016-08-26T10:30:32Z</dc:date>
    </item>
  </channel>
</rss>

