Problem Note 70458: SAS® Micro Analytic Service might fail to start if it contains many modules
 |  |  |  |  |
When you start SAS Micro Analytic Service, it might fail and the last line of sas-microanalyticservice log file might contain the following status message:
System Aborting Status=803fc21e
This issue might occur if the SAS Micro Analytic Service contains many large modules, and it takes more than two hours to load all the modules.
To work around this issue, add the following configuration for Micro Analytic Score service:
key: java_option_check_critical_timeout
value: -Dspring.cloud.consul.discovery.healthCheckCriticalTimeout=3h
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Micro Analytic Service | Microsoft® Windows® for x64 | 5.5 | Viya | ||
| Linux for x64 | 5.5 | Viya | ||||
Viya on Linux: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Linux Deployment Guide at
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.5&softwareContextId=softwareUpdates
When it fails to start, this line occurs in the sas-microanalyticservice log file: "System Aborting Status=803fc21e."
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2023-10-24 09:09:00 |
| Date Created: | 2023-10-20 09:16:03 |