topic Process Engine High Availability in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/process-engine-high-availability/m-p/103393#M72076 <HTML><HEAD></HEAD><BODY><SPAN>Hi All,</SPAN><BR /><BR /><SPAN>Does someone has experience with process engine HA?</SPAN><BR /><SPAN>My scenario is a process engine instantiated programmatically into web application which run on two nodes with session replication.</SPAN><BR /><BR /><SPAN>My big doubt is what happens whether a process engine instantiates a job timer. </SPAN><BR /><SPAN>In case of the first node down, how can the second node manage this job?</SPAN><BR /><BR /><SPAN>Is there any document which explains these aspects? </SPAN><BR /><BR /><SPAN>Thank you so much.</SPAN><BR /><SPAN>Regards</SPAN></BODY></HTML> Tue, 26 Jun 2012 06:46:46 GMT fmasci 2012-06-26T06:46:46Z Process Engine High Availability https://connect.hyland.com/t5/alfresco-archive/process-engine-high-availability/m-p/103393#M72076 Hi All,Does someone has experience with process engine HA?My scenario is a process engine instantiated programmatically into web application which run on two nodes with session replication.My big doubt is what happens whether a process engine instantiates a job timer. In case of the first node down, Tue, 26 Jun 2012 06:46:46 GMT https://connect.hyland.com/t5/alfresco-archive/process-engine-high-availability/m-p/103393#M72076 fmasci 2012-06-26T06:46:46Z Re: Process Engine High Availability https://connect.hyland.com/t5/alfresco-archive/process-engine-high-availability/m-p/103394#M72077 <HTML><HEAD></HEAD><BODY><SPAN>When 2 job-executors are running and one of them goos down while a job/multiple jobs were being executed, the jobs are marked in the database as "locked". After the configurable 'lockTimeInMillis' is expired (search forum for this parameter), the first job-executor will unlock the acquired jobs and run them.</SPAN><BR /><BR /><SPAN>The default timeout is 5 minutes. Note this can potentially cause a max delay of 5 minutes on timers that were being fired on the job executor that was down, but it also allows for jobs that run for more than a minute, not to be ran again because they appear to be "stuck" while the're just still executing. </SPAN><BR /><BR /><SPAN>So to conclude, if multiple job-executors are operating on the same database, and one goes down, the second one will take over the jobs that were executing or where aquired/locked by the job-executor.</SPAN></BODY></HTML> Tue, 26 Jun 2012 06:55:47 GMT https://connect.hyland.com/t5/alfresco-archive/process-engine-high-availability/m-p/103394#M72077 frederikherema1 2012-06-26T06:55:47Z