<?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: Jobs and Clusters in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/jobs-and-clusters/m-p/99666#M68931</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;the fact that some jobs are the lock acquired in another JVM is not an error, this is the normal behavior. So, having some stack traces for that in logs will be annoying for the production team.&amp;nbsp; Yes we can make a filter in java.util.logging, but&amp;nbsp; I just think that would be managed in the code. I just put an 'example', but now while trying to make my own patch, it seems to be a little bit complicated….&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 18 Jul 2012 14:05:59 GMT</pubDate>
    <dc:creator>yblazart</dc:creator>
    <dc:date>2012-07-18T14:05:59Z</dc:date>
    <item>
      <title>Jobs and Clusters</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/jobs-and-clusters/m-p/99664#M68929</link>
      <description>Hi ! I want to install multiple instance of activity, sharing the same database.In my workflows, I will have some timers for example. I made some test.As I read, it's seems that JobExecutor do a 'lock' in the database for each job to execute, so this ensure that the job executor on the other server</description>
      <pubDate>Wed, 18 Jul 2012 12:48:53 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/jobs-and-clusters/m-p/99664#M68929</guid>
      <dc:creator>yblazart</dc:creator>
      <dc:date>2012-07-18T12:48:53Z</dc:date>
    </item>
    <item>
      <title>Re: Jobs and Clusters</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/jobs-and-clusters/m-p/99665#M68930</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;What exactly are you proposing? The monitor lock object? This only works when engines are in the same JVM.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If it's not an error and you don't want to see it logged, can't you exclude it from being logged?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jul 2012 12:52:44 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/jobs-and-clusters/m-p/99665#M68930</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2012-07-18T12:52:44Z</dc:date>
    </item>
    <item>
      <title>Re: Jobs and Clusters</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/jobs-and-clusters/m-p/99666#M68931</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;the fact that some jobs are the lock acquired in another JVM is not an error, this is the normal behavior. So, having some stack traces for that in logs will be annoying for the production team.&amp;nbsp; Yes we can make a filter in java.util.logging, but&amp;nbsp; I just think that would be managed in the code. I just put an 'example', but now while trying to make my own patch, it seems to be a little bit complicated….&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jul 2012 14:05:59 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/jobs-and-clusters/m-p/99666#M68931</guid>
      <dc:creator>yblazart</dc:creator>
      <dc:date>2012-07-18T14:05:59Z</dc:date>
    </item>
  </channel>
</rss>

