topic Re: Activiti Error Handling in Alfresco Archive

Activiti Error Handling

fritz128 — Wed, 25 Sep 2013 15:09:02 GMT

What I have:Non-Activiti processes (saving to DB) in Activiti Service Task. I want to rollback Activiti context on errorWhat a problem:Activiti context doesn't rollback.My code:]In this service task I create new client entity and persist it. Client entity has Unique constraint, so the try{} section

Re: Activiti Error Handling

jbarrez — Thu, 26 Sep 2013 17:11:18 GMT

I don't think any of your questions are asking the correct thing. The question is whether the hibernate session is running in the same transaction as the activiti one. How did you configure that

How can you know that this:

<code>
Engine engine = Engine.getInstance();
SessionFactory sessionFactory = engine.getHibernateSessionFactory();
</code>

is actually in the same transaction

Re: Activiti Error Handling

fritz128 — Fri, 27 Sep 2013 07:21:27 GMT

Thanks for reply

I need to rollback only Activiti's context.
<ul>
<li>Can I make it work without common transaction manager for Activiti and Hibernate? </li>
<li>How can I check that Activiti session factory == Engine.getInstance().getHibernateSessionFactory()? I mean some Activiti's method to get Activiti session factory or where to look at in debug. Please more details</li>
</ul>

Re: Activiti Error Handling

frederikherema1 — Wed, 02 Oct 2013 09:33:07 GMT

1) You cannot make this work (reliably) without having a shared transaction-manager for activiti and your own entities, regardless of the technology (hibernat, jpa, plain JDBC, …).

2) Activiti doesn't use hibernate for persistence…

Re: Activiti Error Handling

fritz128 — Thu, 03 Oct 2013 06:36:19 GMT

Yes, but there are many examples in an internet, where Hibernate's trasaction manager bean are passed to ProcessEngineConfig bean. Is it deliberately wrong way?

Please, see my question http://forums.activiti.org/content/pass-hibernatesessionfactory-activiti-engine-configs

Re: Activiti Error Handling

frederikherema1 — Thu, 03 Oct 2013 08:09:54 GMT

If you're using the hibernate transaction manager as transaction-manager for Activiti, both activiti and your DB-stuff will get rollbacked when transaction rolls back (after error in hibernate or error in activiti execution).

If you DO NOT want your transaction to roll-back when something happens in activiti, don't use the same transaction-manager. However, in case that the activiti-transaction is comitted (and contains a reference to hibernate-entities you created) AND after that, the hibernate-transaction rolls back, you end up with variables in activiti referencing an unexisting entity in your DB. Not sure what the actual usacase is to NOT synchronize the transactions?

Re: Activiti Error Handling

fritz128 — Fri, 04 Oct 2013 11:23:34 GMT

The point is that when I pass HibernateTransactionManager to both Activiti and application, it DOESN'T WORK. There are a lot of topics in the internet that people face the same problem. It is very common issue. And there're any working example (I search a lot) that can confirm your words.

Can you provide me a very simple working demo with Activiti + Spring + common HibernateTransactionManager + desirable with Postgres? PLEASE!

P.S.
In debug I can see that in service tasks Activiti call Context.getCommandContext().getDbSqlSession() that returns org.activiti.engine.impl.db.DbSqlSession instead of hibernate session

see the last comment in http://forums.activiti.org/content/pass-hibernatesessionfactory-activiti-engine-configs question

Re: Activiti Error Handling

frederikherema1 — Wed, 09 Oct 2013 12:42:48 GMT

About the org.activiti.engine.impl.db.DbSqlSession versus the hibernate session: a hibernate-session is used to get Hibernate-entities from. The org.activiti.engine.impl.db.DbSqlSession is an internal session in activiti which gives access to SQL-functionality on top of mybatis. So the hibernate session is really not relevant.

The only thing that is relevant is that, in case the HibernateTransactionManager is used, the underlying datasource returns the same SQL-connection as is used for the hibernate-operations. Can you please share your process-engine configuration (spring-context) so we can validate what settings you're using to accomplish this.

There are a lot of topics in the internet that people face the same problem

Do you mean specifically using activity and hibernate together? Because in Alfresco 3.4.X, activiti was running with the hibernate transaction manager (as all entities USED to be hibernate in alfresco) without any issues and unit-tests to back that statement up…

Re: Activiti Error Handling

pkonyves — Fri, 21 Mar 2014 08:09:58 GMT

Hi, I have a question regarding activiti errors and transactions.

As the userguide says, activities are executed within a DB transaction. If techincal (RuntimeException) is thrown, then the transaction is rolled back leaving the process instance unchanged. Is this the case also when I throw BpmnError?

My problem is that I cannot pass any meaningful error message to a user when an exception occurs, because the db transaction is rolled back, any process variable changes are unmade too. Db transaction must stay rolled back by the way, so that is ok to me. My only problem is how to store a message to show the user after an error?

Error boundary event would be good, but all the information I can pass is the error code which is not enough.

Obviously I could set variables in a new JTA transaction (I use JTA), but it's very inconvenient. Is there some support for my case?

<code>
CommandExecutor commandExecutor = ((ProcessEngineImpl)processEngine).getProcessEngineConfiguration().getCommandExecutor();
      CommandConfig config = new CommandConfig().transactionRequiresNew();
      commandExecutor.execute(config, new Command<Object>() {
        public Object execute(CommandContext commandContext) {
          // do my sh*t here
          return null;
        }
      });
</code>

or using JTA transaction:
<code>
JtaProcessEngineConfiguration jtaProcessEngineConfiguration = (JtaProcessEngineConfiguration) processEngineCfg;
TransactionManager tm = jtaProcessEngineConfiguration.getTransactionManager();
tm.suspend();
tm.begin();
// do my sh*t
tm.commit();
tm.resume(tx);
</code>

Re: Activiti Error Handling

trademak — Fri, 21 Mar 2014 16:01:32 GMT

When you are invoking the process instance synchronously and it executes synchronously you'll get the exception back in your calling application. And you can act on that based on the exception details. Doesn't that work for you?

Re: Activiti Error Handling

pkonyves — Fri, 21 Mar 2014 23:07:21 GMT

I would catch it if I could but we build a gui for Activiti with JSF. Processes have their own facelets for forms with complete buttons like h:commandButton action="BusinessProcess#completeTask(taskId)". I don't think it's the most practical way, but we didn't want to force workflows to use our own API, they can use standard Activiti API the same way Activiti in action describes the JSF integration. I am telling it because this excludes the idea of just wrapping the completeTask() method in a try-catch block.

I can catch the exception in the JSF ErrorHandler and show it to the user: OK. But also want to have it logged within the process to save this information as a process variable for later time. I don't want to do in the JSF ErrorHandler, because I would kill myself for making calls to the business tier from the "last rock" of my application, the ErrorHandler, totally out the JSF lifecycle etc.

I could probably automate this behavior with a custom CommandInterceptor… Anyways, if you don't have a better idea, I think a new transaction is fine.

ps.: You still mentioned synchronously, but I also want it to work on async tasks

Thanks