SAS Solution for IFRS 17 offers a Traceability Tool feature that uses OUTPUT_CALC_LOGIC_FLG. This option controls the logic to enable the output of text files that contain the calculation logic in the initial recognition and subsequent measurement nodes of the SAS Infrastructure Risk Management calculation flows. If you set the option to N, the files are generated without content (Y/N).
The Traceability Tool provides an option in the SAS Risk Governance Framework and International Financial Reporting Standards 17 user interface (UI) to generate additional traceability data. By default, the option is set to false.
In one configuration, the option was set to true and combined with 21K Insurance Cohort Groups (ICGs), which contributed to more than 2GB of traceability data. As a result, an error occurred.
Cause
In this scenario, the SAS Solution for IFRS 17 Cycle Analysis Output Calculation Logic UI option is set to Yes. During the SAS Solution for IFRS 17 AOCA cycle task, the ICG number tanks to 21K, which generates a lot of log data. As a result, the Integrated Object Model (IOM) FlushLog lines method writes to the mvatask log, exceeding the 2GB hard limit currently set, and contributes to the following errors during the cycle task run:
IRM [Thread-238 - Task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=2 )')] 07Aug26 16:04:27,099 DEBUG com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable [] - Ok to proceed was false running task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=2 )')
IRM [Thread-238 - Task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=2 )')] 07Aug26 16:04:27,099 ERROR com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable [] - newLimit > capacity: (1703258179 > 1703258111)
IRM [Thread-238 - Task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=2 )')] 07Aug26 16:04:27,099 DEBUG com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable [] - Setting exception on runnable because retry is false for task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=2 )').
IRM [Thread-238 - Task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=2 )')] 07Aug26 16:04:27,099 DEBUG com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable [] - No setup lines for log output.
IRM [Thread-238 - Task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=2 )')] 07Aug26 16:04:27,099 DEBUG com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable [] - No task lines for log output.
IRM [Thread-238 - Task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=2 )')] 07Aug26 16:04:27,099 DEBUG com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable [] - No tear down lines for log output.
IRM [Thread-238 - Task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=2 )')] 07Aug26 16:04:27,099 DEBUG com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable [] - No log lines to return.
The following messages also occur in the SAS Infrastructure Risk Management Server log:
IRM [Thread-166] 03Aug26 17:25:43,049 INFO com.sas.solutions.risk.irm.server.jobflowexec.JobFlowExecutor [] - The execution of task STS_00_irmif_node_prem_acq_cost_amort(key: 188768894) has completed in 38961 ms with status of COMPLETED_SUCCESS
IRM [Thread-166] 03Aug26 17:25:43,050 INFO com.sas.solutions.risk.irm.server.jobflowexec.JobFlowExecutor [] - All locked entries for executing job flow instance GMM VFA PAA 03AUG2026_171810_C14990 are released.
IRM [Thread-166] 03Aug26 17:25:43,051 INFO com.sas.solutions.risk.irm.server.jobflowexec.JobFlowExecutor [] - unlockJobFlowInstance GMM VFA PAA 03AUG2026_171810_C14990(624864410 after task execution update.
IRM [Thread-369] 03Aug26 17:25:43,053 INFO com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService [] - The execution of task STS_00_irmif_node_subsequent_measurement(key: 1447515511) is not skipped because DataObjectPoolingService did not find its output in the pool.
IRM [Thread-171 - Task ID='_13_partition_exec' ('Internal Java task for executing partitioned node STS_00_irmif_node_subsequent_measurement')] 03Aug26 17:25:43,121 WARN com.sas.solutions.risk.irm.server.taskexec.JavaTaskRunnable [] - Unable to create separate log file for ParallelExecTask [Internal Java task for executing partitioned node STS_00_irmif_node_subsequent_measurement[_13_partition_exec] - Status = RUNNING - Key = 2057934195
- Incoming: []
- Outgoing: []
- Input: []
- Output: []] because the log file path for this task was null or empty.
IRM [Thread-171 - Task ID='_13_partition_exec' ('Internal Java task for executing partitioned node STS_00_irmif_node_subsequent_measurement')] 03Aug26 17:25:43,126 INFO com.sas.solutions.risk.irm.server.taskexec.ParallelExecTask [] - "Parallel execution starts for partitioned task ID="_13" ("STS_00_irmif_node_subsequent_measurement")."
IRM [Thread-163 - Task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=4 )')] 03Aug26 17:25:43,198 INFO com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable [] - Running SAS task ID="_13" ("STS_00_irmif_node_subsequent_measurement (partition rank=4 )") using code from federated area ID="icv.2023.09" and workspace running on "msealxqa09" (logical server index=1, process id=964083, server UUID="915510F1-4E35-B14B-9E3E-88A70AFF3099".).
IRM [Thread-168 - Task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=3 )')] 03Aug26 17:25:43,198 INFO com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable [] - Running SAS task ID="_13" ("STS_00_irmif_node_subsequent_measurement (partition rank=3 )") using code from federated area ID="icv.2023.09" and workspace running on "msealxqa09" (logical server index=1, process id=964296, server UUID="6E2E72F1-3A8B-814A-B3E9-89FD7E5F90CA".).
IRM [Thread-167 - Task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=2 )')] 03Aug26 17:25:43,199 INFO com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable [] - Running SAS task ID="_13" ("STS_00_irmif_node_subsequent_measurement (partition rank=2 )") using code from federated area ID="icv.2023.09" and workspace running on "msealxqa09" (logical server index=1, process id=964708, server UUID="4A2A8FD2-B7B2-E042-BE4E-CBEAB55A9277".).
IRM [Thread-162 - Task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=1 )')] 03Aug26 17:25:43,200 INFO com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable [] - Running SAS task ID="_13" ("STS_00_irmif_node_subsequent_measurement (partition rank=1 )") using code from federated area ID="icv.2023.09" and workspace running on "msealxqa09" (logical server index=1, process id=965071, server UUID="0178E589-4A93-794C-95CA-F87B3F41662A".).
IRM [JobFlowInstanceSweeper-1001] 03Aug26 17:26:15,142 INFO com.sas.solutions.risk.irm.server.admin.JobFlowInstanceSweeper [] - Done running jobflow instance sweeper: 0
IRM [Thread-168 - Task ID='_13' ('STS_00_irmif_node_subsequent_measurement (partition rank=3 )')] 03Aug26 17:30:51,118 FATAL com.sas.iom.orb.brg.Engine [] - (f2B,c0) IOM Bridge for Java encountered an internal error
java.lang.IllegalArgumentException: capacity < 0: (-1956299955 < 0)
at java.nio.Buffer.createCapacityException(Buffer.java:290) ~[?:?]
Workaround
To work around this issue, set the Trace Measure Values flag parameter value to No in the SAS Solution for IFRS 17 Risk Governance Framework Cycle UI page details view ► Model Parameters tab.
Note: It is still useful to set the above parameter option to Yes for smaller volumes. For larger volumes of SAS Solution for IFRS 17 task executions, though, setting the parameter to Yes can cause problems.
Here is an example: