Stackoverflow error when synching offline app

We have an offline tablet app in which users can fill out forms & add extra objects to these forms. When 1 of the users tried to sync data from the offline tablet app we saw the following in the logs: 2018-07-04T23:39:12.69+0000 [APP/PROC/WEB/0]    CRITICAL - ActionManager: Error in execution of monitored action 'commit' (execution id: 1530747545453-331, execution type: CLIENT) 2018-07-04T23:39:12.69+0000 [APP/PROC/WEB/0]    CRITICAL - ActionManager: java.lang.StackOverflowError: null What could be a cause for this? Where should I start looking? Just before this error, there's the following: 2018-07-04T23:39:11.68+0000 [APP/PROC/WEB/0]    WARNING - RequestStatistics: Request state size of 348 objects exceeds the threshold of 100 objects. Request details: type 'commit' in session 'e06be9a2-35c1-48b5-ae60-69ddc52f87bc'. State consists of:  2018-07-04T23:39:11.68+0000 [APP/PROC/WEB/0]     * ConfinedSpaces.AtmosphereTesting: 14 objects 2018-07-04T23:39:11.68+0000 [APP/PROC/WEB/0]     * ConfinedSpaces.ConfinedSpaces: 2 objects 2018-07-04T23:39:11.68+0000 [APP/PROC/WEB/0]     * ConfinedSpaces.ConfinedSpacesAccess: 57 objects 2018-07-04T23:39:11.68+0000 [APP/PROC/WEB/0]     * ConfinedSpaces.ConfinedSpacesForm: 58 objects 2018-07-04T23:39:11.68+0000 [APP/PROC/WEB/0]     * ConfinedSpaces.PreworkAssessment: 57 objects 2018-07-04T23:39:11.68+0000 [APP/PROC/WEB/0]     * ConfinedSpaces.RescueConsiderations: 57 objects 2018-07-04T23:39:11.68+0000 [APP/PROC/WEB/0]     * OfflineTablet.OfflineActivity: 2 objects 2018-07-04T23:39:11.68+0000 [APP/PROC/WEB/0]     * OfflineTablet.OfflineLocation: 2 objects 2018-07-04T23:39:11.68+0000 [APP/PROC/WEB/0]     * SiraFieldToolkit.ActivityPhoto: 99 objects Could this be related?
1 answers

I would start looking at the events of the entity that you are syncing.

Is there an action on before/after commit that commits the object, leading to a stack overflow?

The second error, is a warning stating that the client is requesting more than 100 objects from the sever which might cause a degradation of performance. This does not look to be related to the error, but might be if a loop is created in your app logic. However then this is a side effect and not the cuase for the stackoverflow.