At the time of creation or installation of federation areas during heavy parallelization, instances of ConcurrentModificationException intermittently occur.

An HTTP 500 error is returned when you run the Jenkins pipeline's parallel run tests section.

In addition, the following error occurs in the SASServer8_1 catalina.out file on the middle-tier machine:

<SASConfig>/<Lev#>/Web/WebAppServer/SASServer8_1/logs/catalina.out

[date time],913 [tomcat-http--33] ERROR [sasrwa] com.sas.solutions.risk.irm.server.rest.BaseController - 
java.util.ConcurrentModificationException
    at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:911)
    at java.util.ArrayList$Itr.next(ArrayList.java:861)
    at com.sas.solutions.risk.irm.server.bpmn.model.Process.getFlowElements
(Process.java:258)
    at com.sas.solutions.risk.irm.server.model.JobFlowInstance.getSubFlowInstances
(JobFlowInstance.java:140)
    at com.sas.solutions.risk.irm.server.model.JobFlowInstance.getAllSubFlowInstances
(JobFlowInstance.java:153)
    at com.sas.solutions.risk.irm.server.model.JobFlowInstance.getAllSubFlowInstances
(JobFlowInstance.java:160)
    at com.sas.solutions.risk.irm.server.model.JobFlowInstance.getAllSubFlowInstances
(JobFlowInstance.java:160)
    at com.sas.solutions.risk.irm.server.engine.JobFlowService.hasPersonalFAArtifacts
(JobFlowService.java:6427)
    at com.sas.solutions.risk.irm.server.engine.JobFlowService.getJobFlowInstances
Info(JobFlowService.java:1273)
    at com.sas.solutions.risk.irm.server.rest.JobFlowController.getJobFlow
InstancesInfo_v0(JobFlowController.java:124)
    at sun.reflect.GeneratedMethodAccessor288.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.
java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    .....
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.
java:61)
    at java.lang.Thread.run(Thread.java:750)

Because of a common HashMap or a list used by multiple threads almost simultaneously, some threads result in an exception, which partly halts the pipeless process.

There is no workaround for this issue.

Solution

A code fix for this issue was included in SAS^® Infrastructure for Risk Management 3.8 Hot Fix R2D001. Apply the latest SAS Infrastructure for Risk Management 3.8 Hot Fix to obtain the code fix.

See SAS Infrastructure for Risk Management 3.8 | Hot Fix Downloads for additional information.