Exception Autocommit object detects at the end of the transaction

0
Hi All, Can someone please explain below issue. This stopped the scheduler and roll back all the activities. 2019-07-30 02:56:09.927 ERROR - ActionManager: Exception in execution of monitored action 'ModuleName.MicroflowName' (execution id: 8e54fb97-2ad5-4da4-ae28-f312929e4662, execution type: SCHEDULED_EVENT) 2019-07-30 02:56:09.927 ERROR - ActionManager: com.mendix.systemwideinterfaces.MendixRuntimeException: Autocommitted objects detected at end of transaction for system session for entities:  - ModuleName.EntityName: 1 instances         at com.mendix.basis.action.RequestScope$$anonfun$com$mendix$basis$action$RequestScope$$verifyNoAutoCommitsForSystemSessionExists$1$1.apply(RequestScope.scala:115)         at com.mendix.basis.action.RequestScope$$anonfun$com$mendix$basis$action$RequestScope$$verifyNoAutoCommitsForSystemSessionExists$1$1.apply(RequestScope.scala:113)         at scala.Option.foreach(Option.scala:257)         at com.mendix.basis.action.RequestScope.com$mendix$basis$action$RequestScope$$verifyNoAutoCommitsForSystemSessionExists$1(RequestScope.scala:113)         at com.mendix.basis.action.RequestScope$$anonfun$endTransaction$1.apply(RequestScope.scala:129)         at com.mendix.basis.action.RequestScope$$anonfun$endTransaction$1.apply(RequestScope.scala:126)         at scala.Option.foreach(Option.scala:257)         at com.mendix.basis.action.RequestScope.endTransaction(RequestScope.scala:126)         at com.mendix.basis.action.ContextImpl.endTransaction(ContextImpl.java:204)         at com.mendix.basis.component.InternalCore.commit(InternalCore.java:321)         at com.mendix.basis.component.InternalCore.commit(InternalCore.java:188)         at com.mendix.basis.component.InternalCore.commit(InternalCore.java:166)         at com.mendix.basis.component.InternalCore.commit(InternalCore.java:152)         at com.mendix.basis.actionmanagement.UserScheduledAction.executeScheduledAction(ScheduledAction.scala:82)         at com.mendix.basis.actionmanagement.ScheduledAction$ScheduledRun$$anonfun$run$1.apply(ScheduledAction.scala:133)         at com.mendix.basis.actionmanagement.IMonitoredAction$$anon$1.execute(IMonitoredAction.scala:47)         at com.mendix.util.classloading.Runner.doRunUsingClassLoaderOf(Runner.java:33)         at com.mendix.basis.actionmanagement.IMonitoredAction$class.monitor(IMonitoredAction.scala:49)         at com.mendix.basis.actionmanagement.ScheduledAction$ScheduledRun.monitor(ScheduledAction.scala:124)         at com.mendix.basis.actionmanagement.ScheduledAction$ScheduledRun.run(ScheduledAction.scala:133)         at com.mendix.basis.actionmanagement.ScheduledAction.execute(ScheduledAction.scala:122)         at com.mendix.basis.actionmanagement.ScheduledAction.run(ScheduledAction.scala:103)         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)         at java.lang.Thread.run(Thread.java:748)
asked
2 answers
0

See the documentation here: https://docs.mendix.com/refguide/object-activities

Having autocommitted objects are always modeling errors. You forgot to do a commit on newly created objects somewhere.

Regards,

Ronald

 

answered
0

The check ‘commit’ in activities Create and Change intuitively is the developer saying to the database management of Mendix,

  • if checked: “you have to commit this change now” 
  • if not checked: “commit this change at your own convenience”

Instead “if not checked” Mendix might not commit the change at all. This is a very big error by the Mendix Business Server. No Database-engine should ever drop data. A good thing to know is that Chris de Gelder's idea of removing this feature is planned for implementation. Please upvote this idea, as it might speed up things a bit.

For now, find out which Create or Change activity you have not marked the commit-check and mark it so it gets committed right away.

answered