topic Activiti on Websphere and Spring AsyncJobExcutor in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/activiti-on-websphere-and-spring-asyncjobexcutor/m-p/234903#M188033 <HTML><HEAD></HEAD><BODY><STRONG>Context</STRONG><SPAN> : Make long story short, it has been decided in my company to use Activiti, we have strong knowledge in EMC Workflow Engine. We have deployed it in a hurry in production on IBM Websphere Application Server.</SPAN><BR /><SPAN>Not enough load/perfomance tests, the inevitable happens : the server crashed.</SPAN><BR /><BR /><SPAN>After some investigations, blog posts &amp; forums readings we found a solutions.</SPAN><BR /><BR /><SPAN>[h2]1. Work Manager et Timer Scheduler[/h2]</SPAN><BR /><BR /><SPAN>Managing your own thread on a WAS is never a good idea. Even if the new class ManagedAsyncJobExecutor use a threads pool of the container this is not suitable for the WAS.</SPAN><BR /><SPAN>It use work manager - a pool of threads - and managed it by itself.</SPAN><BR /><BR /><SPAN>I re-wrote the existing DefaultAsyncJobExecutor using the spring class org.springframework.core.task.AsyncTaskExecutor, it works like the java java.util.concurrent.ExecutorService.</SPAN><BR /><SPAN>This interface is mainly implemented by two classes</SPAN><BR /><UL><LI>one for a Servlet Container : org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor</LI><LI>one for a Applicaton Container : org.springframework.scheduling.commonj.WorkManagerTaskExecutor (needs the jndi name of the work manager)</LI></UL><SPAN>&nbsp;&nbsp;&nbsp;</SPAN><BR /><SPAN>The AbstractAsyncJobExecutor starts two threads two retrieve jobs to treat. Regarding the code, this is just a runnable snippet that is scheduled.</SPAN><BR /><BR /><SPAN>I rewrite the two classes AcquireAsyncJobsDueRunnable &amp; AcquireTimerJobsRunnable, the common code (99%) has been mutualized in AbstractAcquireJobsRunnable.</SPAN><BR /><SPAN>I use the time scheduler to avoid Thread.sleep(). I use the Spring implementation because of the WAS, but a standard java one does exist java.util.concurrent.ScheduledExecutorService.</SPAN><BR /><SPAN>I think this is better to use this than a thread.</SPAN><BR /><BR /><SPAN>The philosophy is still the same :</SPAN><BR /><UL><LI>The Async executor starts schedule of execution of the AcquireAsyncJobsDueRunnable &amp; AcquireTimerJobsRunnable</LI><LI>When the scheduler is executed, two tasks are executed by the AsyncTaskExecutor - one for each runnable</LI><LI>They check the database to retrieve jobs and put runnable task for each job in the AsyncTaskExecutor.</LI><LI>if there is no more job to treat or if the queue of the AsyncTaskExecutor is full, the AbstractAcquireJobsRunnable schedule its next execution.</LI></UL><SPAN>I'm a little bit annoyed with the term AsyncJobExecutor because it does more than just executing job. It rerieves jobs to treat and then only executes them.</SPAN><BR /><SPAN>It is more a AsyncJobExecutorManager or something like that.</SPAN><BR /><BR /><SPAN>One more strange thing is that AcquireAsyncJobsDueCmd constructor requires a AsyncJobExecutor object. In fact, it only needs lockTimeInMillis and maxJobsPerAcquistions params.</SPAN><BR /><BR /><SPAN>Globally, the rewriting of the classes is more OOP / Spring compliant.</SPAN><BR /><BR /><SPAN>[h2]2. Transaction Manager[/h2]</SPAN><BR /><BR /><SPAN>We use the inappropriate transactionManager : org.springframework.jdbc.datasource.DataSourceTransactionManager.</SPAN><BR /><SPAN>For WAS, you have to use : org.springframework.transaction.jta.WebSphereUowTransactionManager</SPAN><BR /><BR /><BR /><SPAN>[h2]3. Websphere Application Server Config[/h2]</SPAN><BR /><BR /><SPAN>Define a workmanager :</SPAN><BR /><UL><LI>name : workmanager/listener</LI><LI>Work request queue size　: 0</LI><LI>Work request queue full action　: FAIL</LI><LI>Alarm threads : 15</LI><LI>Minimum threads : 10</LI><LI>Max threads : 200</LI><LI>Threads priority : 5</LI></UL><SPAN>Define a scheduler :</SPAN><BR /><UL><LI>name : timer/listener</LI></UL><BR /><SPAN>[h2]4. Activiti 6 and message queue based async executor[/h2]</SPAN><BR /><BR /><SPAN>The mechanism explained below is applicable for Activiti 6 OOTB.</SPAN><BR /><BR /><SPAN>Following this post </SPAN><A href="http://www.jorambarrez.be/blog/2016/07/20/message-queue-async-executor-benchmark/" rel="nofollow noopener noreferrer">http://www.jorambarrez.be/blog/2016/07/20/message-queue-async-executor-benchmark/</A><SPAN>, we can adapt the mechanism like this based on the producer / consumer pattern.</SPAN><BR /><BR /><UL><LI>Use a scheduler to schedule tasks to retrieve jobs</LI><LI>job are put in a queue (java, jms, whatever.)</LI><LI>use a second scheduler to read this queue and put the job in the workmanager</LI></UL><SPAN>I dont know if it will be more efficient, but it can regulate the load of the executor</SPAN><BR /><BR /><SPAN>Feel Free to ask more details of the solutions.</SPAN><BR /><BR /><SPAN>Thanks for providing such a great product.</SPAN><BR /><BR /><SPAN>Code in attachment, rename it to code.zip</SPAN><BR /><SPAN> </SPAN><BR /></BODY></HTML> Mon, 19 Sep 2016 20:59:00 GMT ggr 2016-09-19T20:59:00Z Activiti on Websphere and Spring AsyncJobExcutor https://connect.hyland.com/t5/alfresco-archive/activiti-on-websphere-and-spring-asyncjobexcutor/m-p/234903#M188033 Context : Make long story short, it has been decided in my company to use Activiti, we have strong knowledge in EMC Workflow Engine. We have deployed it in a hurry in production on IBM Websphere Application Server.Not enough load/perfomance tests, the inevitable happens : the server crashed.After so Mon, 19 Sep 2016 20:59:00 GMT https://connect.hyland.com/t5/alfresco-archive/activiti-on-websphere-and-spring-asyncjobexcutor/m-p/234903#M188033 ggr 2016-09-19T20:59:00Z Re: Activiti on Websphere and Spring AsyncJobExcutor https://connect.hyland.com/t5/alfresco-archive/activiti-on-websphere-and-spring-asyncjobexcutor/m-p/234904#M188034 <HTML><HEAD></HEAD><BODY><P>Hello GGR, this is fantastic work that I expect will be very useful for other community members.<BR />Would Fujitsu be prepared to contribute this as an alternative Job Scheduler?</P><P>Thanks,<BR />Greg</P><P><A href="https://migration33.stage.lithium.com/t5/tag/bp3/tg-p"></A>‌</P></BODY></HTML> Thu, 15 Dec 2016 14:45:28 GMT https://connect.hyland.com/t5/alfresco-archive/activiti-on-websphere-and-spring-asyncjobexcutor/m-p/234904#M188034 gdharley 2016-12-15T14:45:28Z