65592 - SAS® Infrastructure for Risk Management fails to execute parallel Current Expected Credit Loss scenario jobs

Problem Note 65592: SAS® Infrastructure for Risk Management fails to execute parallel Current Expected Credit Loss scenario jobs

When you attempt to run parallel Current Expected Credit Loss jobs in SAS Infrastructure for Risk Management, the job execution fails. When this happens, the following error messages are found in the SAS Infrastructure for Risk Management log:

IRM [Thread-48357 - Task ID='_3' ('STS_00_irmcecl_node_init')] 28Oct19

10:35:03,258 ERROR com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable  - An exception was thrown while waiting for a reply from the peer.

org.omg.CORBA.COMM_FAILURE: An exception was thrown while waiting for a reply from the peer.  vmcid: 0x0  minor code: 0  completed: No

   at com.sas.iom.orb.brg.Engine.waitForReply(Engine.java:1957)

   at com.sas.iom.orb.brg.Engine.sendRequest(Engine.java:885)

   at com.sas.iom.orb.brg.RequestImpl.invoke(RequestImpl.java:37)

   at com.sas.iom.SAS._portable_stub_ILanguageService.SubmitLines(_portable_stub_ILangageService.java:270)

   at com.sas.solutions.risk.irm.server.taskexec.SASIOMWorkspaceHolder.executeSASCode(SASIOMWorkspaceHolder.java:292)

   at com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable.executeSASCode(MvaTaskRunnable.java:1388)

   at com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable.executeAllAndGetResults(MvaTaskRunnable.java:1542)

   at com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable.run_local(MvaTaskRunnable.java:901)

   at com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable.run(MvaTaskRunnable.java:535)

   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

   at java.util.concurrent.FutureTask.run(FutureTask.java:266)

   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

   at java.lang.Thread.run(Thread.java:748)

Caused by: java.io.IOException: The communication channel with the peer closed unexpectedly.

   at com.sas.iom.orb.brg.Engine.readFully(Engine.java:7466)

   at com.sas.iom.orb.brg.Engine.readEncryptedPacket(Engine.java:5905)

   at com.sas.iom.orb.brg.Engine.recvPacket(Engine.java:5885)

   at com.sas.iom.orb.brg.Engine.listen(Engine.java:2518)

   at com.sas.iom.orb.brg.Engine.waitForReply(Engine.java:1991)

   . . .13 more message lines. . .

For assistance from SAS Technical Support to resolve this issue, perform the following steps to put the SASIRMServer.log file into DEBUG mode:

Locate the following code in the SASIRMServer-logj4.xml file:

   <logger name="com.sas.solutions.risk.irm" additivity="false">
    <level value="INFO" />
      <appender-ref ref="SAS_FILE"/>
     <appender-ref ref="SAS_CONSOLE"/>
   </logger>
Change the VALUE="INFO" parameter to VALUE="DEBUG", as shown below:

   <logger name="com.sas.solutions.risk.irm" additivity="false">
      <level value="DEBUG" />
      <appender-ref ref="SAS_FILE"/>
      <appender-ref ref="SAS_CONSOLE"/>
   </logger>
Restart SASServer 8 and re-create the issue. Send the contents of the SASIRMServer.log to SAS Technical Support.
After you send the log to Technical Support, change the VALUE="DEBUG" option back to VALUE="INFO" in the SASIRMServer-logj4.xml file.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Infrastructure for Risk Management	Linux for x64	3.5	3.6	9.4 TS1M5	9.4 TS1M6
		Microsoft® Windows® for x64	3.5	3.6	9.4 TS1M5	9.4 TS1M6

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

Type:	Problem Note
Priority:	medium

Date Modified:	2020-02-25 09:35:59
Date Created:	2020-02-20 11:41:50