Announcement

**Isomorphic** · 20 Nov 2013, 15:27

Assuming you're using the Automatic Transactions feature, this suggests that you've got a queue of requests, one of them has failed, causing transaction rollback, and yet you've got logic in a DMI that still tries to execute a request after this failure has occurred:

at com.isomorphic.datasource.DSRequest.execute(DSRequest.java:2431) [isc_isomorphic_core_rpc.jar:na]

at qa.gov.moi.erp.web.dmi.DepartmentMainDMI.fetch(DepartmentMainDMI.java:46) ~[classes/:na]

You can check for the condition of a failure earlier in the queue via the server-side API RPCManager.queueHasFailures().

**Abdulaziz A.** · 1 Dec 2013, 21:41

do you mean by the "Automatic Transactions feature" the autoJoinTransactions. in my server.properties I am not setting the value of the autoJoinTransactions and not in my code as well. so autoJoinTransactions is kept as the default value

please to elaborate as this is urgent issue

**Isomorphic** · 1 Dec 2013, 23:16

For urgent issues, be sure to provide as much information as you can, make good use of the docs, and thoroughly investigate possibly causes that are raised by Support.

This is the most important aspect of solving your problems quickly, as we will not be able to do much for you if you provide information that is too limited, and of course the problem will not get closer to resolution if you ignore Support's advice.

Yes, we were referring to the autoJoinTransactions feature. It is automatically on (as the documentation tells you) unless you've disabled it. You haven't provided complete server logs (as the forums reminds you to do every time), otherwise, we would have been able to see clearly from the logs whether the feature is enabled.

As far as the issue you're having, here again is the possible cause we suggested:

Assuming you're using the Automatic Transactions feature, this suggests that you've got a queue of requests, one of them has failed, causing transaction rollback, and yet you've got logic in a DMI that still tries to execute a request after this failure has occurred

With the information you've provided, we can't investigate this possible cause, but you can.

Announcement

Error : Attempt to continue working after transaction rolledback !

Comment

Comment

Comment