Logs for autocommitted

0
Hi all,  　 We saw auto committed log as below and have some questions. 　 1.Please tell us specifically how to identify the cause of the log occurrence. 　 2.Can you really say that the data is gone with this log ?   Many thanks,  Akira 　 　  [APP/PROC/WEB/0]   WARNING - Core: Some autocommitted objects still existed on logout for session '**************'.  [APP/PROC/WEB/0]   Autocommitted objects are newly created objects which were not yet committed, but are inserted into the database because an associated object was committed.  [APP/PROC/WEB/0]   Autocommitted objects should explicitly have been committed, please check your model and apply the necessary changes. The autocommitted objects have been deleted from the database to prevent database corruption.Number of autocommitted objects per type which still existed for this session: [APP/PROC/WEB/0]   - System.AutoCommitEntry: 3 object(s).  [APP/PROC/WEB/0]   - ********Module.(***Entityname): 3 object(s).
asked
3 answers
0

Hi Akira,

The data will still be stored in the database. It gets automatically commited, because an associated entity has been commited. This usually occurs since the objects mentioned in the error message are created but never committed.

 

To find out where this error comes from you should go to your domain model and look for the entity that is mentioned in the error message. Right click and select find usages in actions. Look through all places where this object is created and try to identify if it is created somewhere, without being commited. Add a commit there and it should solve the problem. The error message doesn't show the exact code that makes this happen, so you will have to research it a bit.

 

Hope this helps!

answered
0

Hi buddy this might help you to know the cause for occurrence 
 

Here is an example domain model that showcases this situation:

Example domain model with an Customer and Order entity, connected by an one-to-many association which indicates a Customer can have multiple Orders

To continue the example, here is the related nanoflow:

A nanoflow creating a Customer and an Order, associating them, and only committing the Order instance

The example above saves the $NewOrder object to the local database, including the association value referencing the uncommitted $NewCustomer object. Since the $NewCustomer is not yet committed, however, the reference is invalid. To solve this issue, the nanoflow must commit the $NewCustomer object.

for more details please refer https://docs.mendix.com/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/auto-committed-objects/

answered
0

Hi, Matteo & Mohamedbeemubeen

 

First of all, appriciated your rapidly and kindly reply for my questons.

 

We shared you guys information with our team members.

Hopefully our issue would be solved with this info.

just contined to investigate which actions cause this issue.

 

thanks again.

Akira

answered