Empty error message after deadlock

In Mendix 2.4 beta 4, we recieve an empty error pop-up after a deadlock. The deadlock is handled in the code and works fine, but recently an empty error appears when retrying the same action that caused the deadlock. The result is that the action can not be succesfully performed. The empty error is definitely not triggered by a microflow or java-action, it seems to be generated by the framework. The only known solution is to restart the XAS, after which the action works fine. Is this a known bug? Is there a way to prevent it, or to solve it without a restart? Is the fact that the deadlocked action involves a webservice important? Thanks in advance for any help.
3 answers

In Mendix 2.4 beta 4

First of all, try upgrading to version 2.4.6 if you're in 2.4. The beta's before 2.4.0 got released are not supported for production use.

we recieve an empty error pop-up after a deadlock

What sort of deadlock (java threads?, database transactions?)? What sort of action is being executed that results in a deadlock?

Do you have a project which can be used to reproduce the problem?


Sadly, upgrading to another version is not an option. The action is a microflow action which generates objects that are sent via a webservice. As I said, the deadlock is a common occurence and not a problem, but the empty error is new, and very much a problem since it prevents retrying the action until resetting the XAS.

This is the log entry:


ERROR - CONNECTIONBUS_RETRIEVE: JDBCDataStore::execRetrieveQuery failed with SQLState: 40001 Message: Transaction (Process ID 74) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.



This problem typically occurs when you have an action (MF or java) which invokes an other action, and both actions write to the same table, but are executed in a different context/ session.