Process step (task) seldomly failed without clear reasons

Description

Dears,

We are having an issue with one of our Bonita process on our production server. As an overview, our diagram works as below flow:

Step 1- submitOrder: User submit an order by filling the submitOrder form
Step 2- reviewOrder: Manager reviews the order and can approve or reject. If approved the order is sent to a third-party application (in our case SAP business one) through the use of a custom connector.
Step 3- pickingList: After order is sent, the process goes on with item picking etc..
Our problem is that, seldom and randomly, it happens that one order failed at step 2. The order is correctly sent to the third-party application after reviewer approval, but for an unclear reason to us, the process sticks here and does not pass to step 3.

This happens very randomly for about 1 order ever 200-300 orders processed through our app. In the Portal as Admin, we see that this case has failed with one failed flow node.

This is what we get from the Bonita server logs (see below, I put in bold and italic the unusual SEVERE error that we get for failed orders, the rest is standard logs for every order processed successfully)

2020-04-15 08:49:10.951 +0000 SEVERE: org.bonitasoft.console.common.server.login.credentials.LoginDatastore Error while logging in the engine API.
2020-04-15 08:49:36.128 +0000 SEVERE: org.bonitasoft.console.common.server.login.credentials.LoginDatastore Error while logging in the engine API.
2020-04-15 08:50:44.123 +0000 SEVERE: org.bonitasoft.console.common.server.login.credentials.LoginDatastore Error while logging in the engine API.
2020-04-15 08:50:46.630 +0000 WARN: com.arjuna.ats.jta ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMFAIL
com.mysql.cj.jdbc.MysqlXAException: Undetermined error occurred in the underlying Connection - check your data for consistency
at com.mysql.cj.jdbc.MysqlXAConnection.mapXAExceptionFromSQLException(MysqlXAConnection.java:347)
at com.mysql.cj.jdbc.MysqlXAConnection.recover(MysqlXAConnection.java:189)
at com.mysql.cj.jdbc.MysqlXAConnection.recover(MysqlXAConnection.java:117)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:634)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:226)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:171)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:770)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:382)

We really don't know if this error while logging can justify this failure, while the process is correctly started, and step 2 and 3 are handled one after the other in the same diagram.

Any idea about the cause of this issue. Any help will be greatly appreciated.

In advance, thank you very much.

Kindest regards,

Environment

Bonita Engine - Porduction server

External Link

None

Workaround

None

Assignee

Delphine Coille

Reporter

Timothe Delhaise

Affects versions

Reference

None

Fix versions

None
Configure