<?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 JobExecutorActivate configuration question in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/jobexecutoractivate-configuration-question/m-p/147505#M102963</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;In a clustered environment when there are 2 activiti engines configured with JobExecutorActivate to true (for load balancing purpose), I observed instances where JobExecutor thread from 2 nodes (engines) are trying to acquire Jobs at the same time and one thread ends up throwing following exception&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;SEVERE: Error while closing command context&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;org.activiti.engine.ActivitiOptimisticLockingException: TimerEntity[e3ca0cba-b1c1-11e2-9038-005056b90423] was updated by another transaction concurrently&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So, Is there a way to configure JobExecutor to run on specific intervals like specifying a Cron Expression for Quartz ?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 01 May 2013 13:47:12 GMT</pubDate>
    <dc:creator>badrisudheer</dc:creator>
    <dc:date>2013-05-01T13:47:12Z</dc:date>
    <item>
      <title>JobExecutorActivate configuration question</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/jobexecutoractivate-configuration-question/m-p/147505#M102963</link>
      <description>In a clustered environment when there are 2 activiti engines configured with JobExecutorActivate to true (for load balancing purpose), I observed instances where JobExecutor thread from 2 nodes (engines) are trying to acquire Jobs at the same time and one thread ends up throwing following exceptionS</description>
      <pubDate>Wed, 01 May 2013 13:47:12 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/jobexecutoractivate-configuration-question/m-p/147505#M102963</guid>
      <dc:creator>badrisudheer</dc:creator>
      <dc:date>2013-05-01T13:47:12Z</dc:date>
    </item>
    <item>
      <title>Re: JobExecutorActivate configuration question</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/jobexecutoractivate-configuration-question/m-p/147506#M102964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Those exception are to be expected when running in a clustered job executor environment. Both executors 'fight' for jobs and one of them has to lose.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In a more recent version of Activiti, we've moved down the level of that log and made the logging more clear that this is an expected thing in a clustered environment.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 May 2013 09:16:19 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/jobexecutoractivate-configuration-question/m-p/147506#M102964</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2013-05-02T09:16:19Z</dc:date>
    </item>
  </channel>
</rss>

