Problem Note 62950: The activation of decision flows fails if the activation takes more than one minute
The activation of decision flows from any of the following components fails when the activation takes more than a minute:
- BatchActivator command-line utility
- SAS® Decision Services Administrative application programming interface (API)
- SAS Decision Services Monitor
- SAS Decision Services plug-in for SAS® Management Console
The following error is typically found in the log when the failure occurs:
12:05:44 ERROR The SAS Decision Services engine could not be updated. The repository changes will be rolled back.
com.sas.analytics.ph.RTDMException: org.springframework.remoting.RemoteAccessException: Could not access HTTP invoker remote service at [http: //<hostname>: 8680 / RTDM / Manager]; nested exception is java.net.SocketTimeoutException: Read timed out
at com.sas.rtdm.EngineConnector $ 1.invoke (EngineConnector.java:69)
. . .more message lines. . .
Caused by: org.springframework.remoting.RemoteAccessException: Could not access HTTP invoker remote service at [http: //<hostname>: 8680 / RTDM / Manager]; nested exception is java.net.SocketTimeoutException: Read timed out
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.convertHttpInvokerAccessException (HttpInvokerClientInterceptor.java:212)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke (HttpInvokerClientInterceptor.java:145)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0 (Native Method)
at java.net.SocketInputStream.read (SocketInputStream.java:152)
Click the Hot Fix tab in this note to access the hot fix for this issue.
The hot fix addresses the issue by providing the following:
- a new command-line option (-t) to specify the timeout value in milliseconds for the BatchActivator command-line utility
- a new configuration item (sasds.adminapi.engine.read.timeout) for the SAS Decision Services Administrative API
- a new configuration item (sasds.monitor.engine.read.timeout) for SAS Decision Services Monitor
- the SAS Decision Services plug-in for SAS Management Console, which waits indefinitely for the activation to complete
You need to change the configuration items listed above in the Configuration Manager plug-in for SAS Management Console. The default value is 60 seconds. To override the default value, create an entry on the Advanced tab and specify the value in milliseconds.
Operating System and Release Information
SAS System | SAS Decision Services | Microsoft® Windows® for x64 | 6.4 | 6.4_M1 | 9.4 TS1M2 | 9.4 TS1M5 |
64-bit Enabled AIX | 6.4 | 6.4_M1 | 9.4 TS1M2 | 9.4 TS1M5 |
64-bit Enabled Solaris | 6.4 | 6.4_M1 | 9.4 TS1M2 | 9.4 TS1M5 |
HP-UX IPF | 6.4 | 6.4_M1 | 9.4 TS1M2 | 9.4 TS1M5 |
Linux for x64 | 6.4 | 6.4_M1 | 9.4 TS1M2 | 9.4 TS1M5 |
Solaris for x64 | 6.4 | 6.4_M1 | 9.4 TS1M2 | 9.4 TS1M5 |
*
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.
The activation of decision flows fails when the activation takes more than one minute. The failure occurs because the timeout value for the HTTP call is always set to the default timeout of 60000 milliseconds when it calls the SAS® Real-Time Decision Manager engine.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2018-10-11 09:36:14 |
Date Created: | 2018-09-19 09:40:13 |