topic Re: Exception handling for Async executor in Alfresco Archive

Exception handling for Async executor

nixikanius — Mon, 17 Oct 2016 14:13:37 GMT

I want to implement global exception handling like it suggested to do for Job executor (http://flaviodonze.blogspot.ru/2013/04/activiti-overall-exception-handlingin.html). To do this I added configuration in activiti-custom-context.xml for activiti-rest:<?xml version="1.0" encoding="UTF-8"?>&l

Re: Exception handling for Async executor

nixikanius — Tue, 25 Oct 2016 12:16:18 GMT

Anybody can help me? I see in sources there is support for custom error handler:

<code>
CommandConfig commandConfig = commandExecutor.getDefaultConfig().transactionRequiresNew();
        FailedJobCommandFactory failedJobCommandFactory = commandContext.getFailedJobCommandFactory();
        Command<Object> cmd = failedJobCommandFactory.getCommand(job.getId(), exception);

        log.trace("Using FailedJobCommandFactory '" + failedJobCommandFactory.getClass() + "' and command of type '" + cmd.getClass() + "'");
</code>

But it does not work. In enabled trace level log I do not see any "Using FailedJobCommandFactory" string even using default error handling.

Re: Exception handling for Async executor

cjose — Wed, 26 Oct 2016 06:03:10 GMT

I just tested your code by turning on the old job executor
<code>
<property name="jobExecutorActivate" value="true" />
</code>
as well as the new Async Executor
<code>
<property name="asyncExecutorEnabled" value="true" />
<property name="asyncExecutorActivate" value="true" />
</code>

In both cases it is behaving correctly where I can see HELLO1! & HELLO2! getting printed in logs.

Regards,
Ciju

Re: Exception handling for Async executor

nixikanius — Mon, 31 Oct 2016 10:14:58 GMT

cjose, thank you for you answer! With asyncExecutorActivate it work perfectly.

Meanwhile I do not understand how task processing works if I do not activate Job Executor and do not activate Async Executor. As I see everything works perfectly except custom error handling. Why does it happen? I thought that Job Executor is activated by default.