http://jira.mobinets.com/jira This file is an XML representation of an issue en-us 6.1.4 6159 19-11-2013 http://jira.mobinets.com/jira/browse/LS-922 L3 Support <p>We found this exception for 2237 request. Please check and advise.<br/> Cause: java.sql.SQLIntegrityConstraintViolationException: ORA-02291: integrity constraint (SRD_PROD.ACT_FK_EXE_SUPER) violated - parent key not found</p> LS-922

[External Mail]RE: ATM312 Ramiz Ibri - Link Down - Request 2237

Bug Normal Ready for QA Unresolved Abdulrahman Dabboussi Abdulrahman Dabboussi Thu, 5 Feb 2026 08:21:38 +0200 Fri, 3 Apr 2026 16:32:17 +0300 SRD Thu, 12 Feb 2026 00:00:00 +0200 0 3 0 minutes 6 hours <p>srd log below </p> <p><a href="https://mobinets-my.sharepoint.com/:u:/p/mohan_rathor/IQDJ39gVW4LxSqDMo8h89mkWATWPgBNJYbZtw_XClpD3e9I?e=juy6xq" class="external-link" rel="nofollow">https://mobinets-my.sharepoint.com/:u:/p/mohan_rathor/IQDJ39gVW4LxSqDMo8h89mkWATWPgBNJYbZtw_XClpD3e9I?e=juy6xq</a></p> <p>Following our analysis of the recent failures , we have identified the root cause and implemented a corrective solution. Please find the details below.<br/> Root Cause<br/> The issue was caused by a concurrency behavior related to Flowable’s asynchronous execution. Specifically, the use of completeAsync="true" on the Feasibility Acceptance subprocess could, under certain conditions, allow the subprocess to start before the parent execution was fully committed in the database, resulting in an Oracle integrity constraint violation (ORA-02291).<br/> Non-Deterministic Behavior<br/> This behavior is non-deterministic and does not occur for all process instances. It typically manifests under high server load or when multiple process instances are executed in parallel, depending on thread scheduling and transaction timing.<br/> Solution Implemented<br/> In the new version of the process, we have removed completeAsync="true" from the Feasibility Acceptance subprocess. This change ensures that the subprocess starts only after all parent executions and preceding call activities have been fully completed, thereby preventing the ORA-02291 error.<br/> All other call activities remain asynchronous in order to maintain optimal performance.<br/> For the production-related request, we performed a “Start Over”, and the requests completed successfully following the happy path without uploading the new BPMN.<br/> Since this issue occurs only under load conditions, we kindly recommend deploying the updated process to the staging environment and conducting a stress test. While the fix is theoretically sound, this additional validation will help confirm the stability and robustness of the solution.</p> <p>pending stress test on staging b4 apply new process on PROD </p> Actual Start Thu, 5 Feb 2026 00:00:00 +0200 Baseline End Thu, 12 Feb 2026 00:00:00 +0200 Baseline Start Thu, 12 Feb 2026 00:00:00 +0200 Customer Date of Baselining Thu, 5 Feb 2026 13:53:15 +0200 Dev. Actual Duration Gantt Options Last Comment <p style="display:inline"><b>Evaluation License Error:</b> EXPIRED</p> Original Estimate PDM Actual Duration Planned End Thu, 12 Feb 2026 00:00:00 +0200 Planned Start Thu, 12 Feb 2026 00:00:00 +0200 Product Rank 0|xtix0h: Rank (Obsolete) 9223372036854775807 VTDirections