I was pleased to see Tijs' posting in July, http://bpmn20inaction.blogspot.com/2014/07/activiti-516-feature-preview.html, announcing that version 5.16 adds support for joining async non-exclusive gateways no longer required using Apache Camel (or similar) to avoid optimistic locking exceptions on the joining gateway.
However when I try out the simple example in the posting, it does not seem to work. Can someone point me to the errors in my ways, I've been trying various approaches but as yet have no success.
Details below, my intent is to reproduce Tijs example above.
Tomcat console output: Starting Process ID Process2 Executing activity: Task 2 Executing activity: Task 1 Exception in thread "pool-1-thread-1" org.activiti.engine.ActivitiOptimisticLockingException: ProcessInstance[8428] was updated by another transaction concurrently at org.activiti.engine.impl.db.DbSqlSession.flushUpdates(DbSqlSession.java:562) at org.activiti.engine.impl.db.DbSqlSession.flush(DbSqlSession.java:444) at org.activiti.engine.impl.interceptor.CommandContext.flushSessions(CommandContext.java:170) at org.activiti.engine.impl.interceptor.CommandContext.close(CommandContext.java:117) at org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:66) at org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:31) at org.activiti.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:40) at org.activiti.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:35) at org.activiti.engine.impl.jobexecutor.ExecuteJobsRunnable.run(ExecuteJobsRunnable.java:46) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)