<?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: Activiti Job Executor EE available (Apache License 2.0) in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159427#M113460</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;A simple reason: Threads of a self managed thread pool will not be managed by the Application Server. E.g. in startup/shutdown scenarios, this means, that these threads can not rely on resources of the application server at any time. The JCA adapter is by design fully integrated into the lifecycle of an application server.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Easier Concurrency Support for JEE applications comes with JSR 236 Concurrency Utils for EE. This is available on the EE7 platform and defines extensions to the SE concurrency APIs to allow them to be used in an app server environment. On JEE5 &amp;amp; JEE6 platforms the only safe way to spawn threads is the WorkManager of an Resource Adapter. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Because implementing such an Resource Adapter requires good knowledge about the JCA contracts,&amp;nbsp; the Activiti Job Executor EE project provides an open source reference.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Nov 2013 10:54:27 GMT</pubDate>
    <dc:creator>catandgrep</dc:creator>
    <dc:date>2013-11-04T10:54:27Z</dc:date>
    <item>
      <title>Activiti Job Executor EE available (Apache License 2.0)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159423#M113456</link>
      <description>Dear Activity Community,We (agito) would like to share our Job Executor for EE environments with you, that we've implemented some time ago for the EE distributions of our product agito BPMO. Due to its loosly coupled nature, it can be integrated with any Activiti Engine.The default job executor in A</description>
      <pubDate>Tue, 13 Aug 2013 09:13:57 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159423#M113456</guid>
      <dc:creator>catandgrep</dc:creator>
      <dc:date>2013-08-13T09:13:57Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti Job Executor EE available (Apache License 2.0)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159424#M113457</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Nice work guys! Keep up the good work!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2013 11:55:06 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159424#M113457</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2013-08-14T11:55:06Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti Job Executor EE available (Apache License 2.0)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159425#M113458</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Version 1.0.8 Released containg upgrade to Activiti 5.14.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The Job Executor EE is available on &lt;/SPAN&gt;&lt;A href="https://github.com/agito-it/activiti-jobexecutor-ee" rel="nofollow noopener noreferrer"&gt;github&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Nov 2013 14:43:22 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159425#M113458</guid>
      <dc:creator>catandgrep</dc:creator>
      <dc:date>2013-11-01T14:43:22Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti Job Executor EE available (Apache License 2.0)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159426#M113459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;&amp;lt;blockquote&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The default job executor in Activiti uses a self managed Thread Pool, which is not sufficient when running Activiti on JEE compliant application servers. Also the hard coupling between process engine and job acquisition does not fit well into enterprise scenarios.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;/blockquote&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Can you expand on why this is? What's missing and/or inferior about the normal implementation?&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Nov 2013 15:43:53 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159426#M113459</guid>
      <dc:creator>clstokes</dc:creator>
      <dc:date>2013-11-01T15:43:53Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti Job Executor EE available (Apache License 2.0)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159427#M113460</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;A simple reason: Threads of a self managed thread pool will not be managed by the Application Server. E.g. in startup/shutdown scenarios, this means, that these threads can not rely on resources of the application server at any time. The JCA adapter is by design fully integrated into the lifecycle of an application server.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Easier Concurrency Support for JEE applications comes with JSR 236 Concurrency Utils for EE. This is available on the EE7 platform and defines extensions to the SE concurrency APIs to allow them to be used in an app server environment. On JEE5 &amp;amp; JEE6 platforms the only safe way to spawn threads is the WorkManager of an Resource Adapter. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Because implementing such an Resource Adapter requires good knowledge about the JCA contracts,&amp;nbsp; the Activiti Job Executor EE project provides an open source reference.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Nov 2013 10:54:27 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159427#M113460</guid>
      <dc:creator>catandgrep</dc:creator>
      <dc:date>2013-11-04T10:54:27Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti Job Executor EE available (Apache License 2.0)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159428#M113461</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Does this work in a clustered environment? Can the resource adapter assign work to multiple jvms in a cluster but have only one jvm pick up work?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Aug 2014 02:18:41 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-job-executor-ee-available-apache-license-2-0/m-p/159428#M113461</guid>
      <dc:creator>mahavirj</dc:creator>
      <dc:date>2014-08-03T02:18:41Z</dc:date>
    </item>
  </channel>
</rss>

