When setting as current version in CMS, the following errors are seen in the CAST-MS log, Refer to the page CAST Management Studio - Information - How to find logs to locate this log.This error causes the operation to stop:
An error has occurred while communicating with the remote log client. The error is as follows
Insufficient system resources exist to complete the requested service
com.castsoftware.util.logger.exceptions.FatalLogException
Here's the full list of messages captured in the log:
2016-04-28 09:36:14.779 ERROR An error has occurred while communicating with the remote log client
com.castsoftware.util.logger.exceptions.FatalLogException:
at com.castsoftware.util.logger.specialized.ProtobufLogWriter.printMessage(ProtobufLogWriter.java:195)
at com.castsoftware.util.logger.specialized.ProtobufLogWriter.logMessage(ProtobufLogWriter.java:250)
at com.castsoftware.util.logger.RemoteLogServer.readLogMessage(RemoteLogServer.java:371)
at com.castsoftware.util.logger.RemoteLogServer.readRemoteLog(RemoteLogServer.java:345)
at com.castsoftware.util.logger.RemoteLogServer.run(RemoteLogServer.java:227)
at java.lang.Thread.run(Thread.java:744)
at com.castsoftware.util.logger.Logging$1.run(Logging.java:461)
Caused by java.io.SyncFailedException:sync failed
at java.io.FileDescriptor.sync(FileDescriptor.java:-2)
at com.castsoftware.util.logger.specialized.ProtobufLogWriter.printMessage(ProtobufLogWriter.java:190)
at com.castsoftware.util.logger.specialized.ProtobufLogWriter.logMessage(ProtobufLogWriter.java:250)
at com.castsoftware.util.logger.RemoteLogServer.readLogMessage(RemoteLogServer.java:371)
at com.castsoftware.util.logger.RemoteLogServer.readRemoteLog(RemoteLogServer.java:345)
at com.castsoftware.util.logger.RemoteLogServer.run(RemoteLogServer.java:227)
at java.lang.Thread.run(Thread.java:744)
at com.castsoftware.util.logger.Logging$1.run(Logging.java:461)
2016-04-28 09:36:14.844 WARNING An error has occurred while closing the log file
java.io.FileNotFoundException:I:\Logs\deployment_deploy.castlog2 (Insufficient system resources exist to complete the requested service)
at java.io.RandomAccessFile.open(RandomAccessFile.java:-2)
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:241)
at com.castsoftware.util.logger.parser.ProtobufLogParser.<init>(ProtobufLogParser.java:233)
at com.castsoftware.util.logger.parser.ProtobufLogStatistics.readFile(ProtobufLogStatistics.java:57)
at com.castsoftware.dmt.model.tasks.utilities.CommandPluginTask.finallyAfterExecution(CommandPluginTask.java:106)
at com.castsoftware.dmt.model.tasks.utilities.CommandLineTask.executeProcess(CommandLineTask.java:345)
at com.castsoftware.dmt.model.tasks.utilities.CommandLineTask.documentExecute(CommandLineTask.java:318)
at com.castsoftware.mda.impl.MemoryTask.execute(MemoryTask.java:82)
at com.castsoftware.java.treatment.Task.run(Task.java:275)
at com.castsoftware.java.treatment.Task.runChildren(Task.java:388)
at com.castsoftware.mda.impl.MemoryAction.execute(MemoryAction.java:253)
at com.castsoftware.mda.impl.MemoryAction.topExecute(MemoryAction.java:246)
at com.castsoftware.mda.transactions.SectionAction.runInternal(SectionAction.java:44)
at com.castsoftware.mda.transactions.Section.runInTransaction(Section.java:192)
at com.castsoftware.mda.transactions.Section.run(Section.java:137)
at com.castsoftware.mda.transactions.Section.runHeadless(Section.java:308)
at com.castsoftware.mda.run.ConfigurationManager.runVerb(ConfigurationManager.java:512)
at com.castsoftware.mda.run.ConfiguredApplication.onTreatment(ConfiguredApplication.java:386)
at com.castsoftware.deliverytool.CLI.onTreatment(CLI.java:98)
at com.castsoftware.mda.run.ConfiguredApplication$2.call(ConfiguredApplication.java:238)
at com.castsoftware.mda.run.ConfiguredApplication$2.call(ConfiguredApplication.java:1)
at com.castsoftware.util.logger.Logging.execute(Logging.java:500)
at com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:389)
at com.castsoftware.mda.run.ConfiguredApplication.run(ConfiguredApplication.java:227)
at com.castsoftware.deliverytool.CLI$1.call(CLI.java:41)
at com.castsoftware.deliverytool.CLI$1.call(CLI.java:1)
at com.castsoftware.util.logger.Logging.execute(Logging.java:500)
at com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:389)
at com.castsoftware.deliverytool.CLI.main(CLI.java:32)
at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.castsoftware.bootstrap.JarBootstrap.executeMain(JarBootstrap.java:529)
at com.castsoftware.bootstrap.JarBootstrap.main(JarBootstrap.java:755)
2016-04-28 09:36:14.893 ERROR com.castsoftware.util.logger.exceptions.FatalLogException
Release | Yes/No |
|---|---|
| 8.3.x |  |
RDBMS | Yes/No |
|---|---|
| CSS | |
Below is the step-by-step scenario leading to the problem:
- Deliver code through the DMT process.
- Run set as current version in Cast Management Studio (CMS).
The impact of the problem on the analysis or the dashboard is: No further action can be done until the issue is remediated.
To fix the problem, proceed as follows:
- Make sure that the log location has enough space for the application.
- If the log location is on a network drive, make sure that it is accessible and available for writing.
You can specify the log location in CAST-MS in the menu item Windows->preferences as shown in the screenshot below:
