Article - CS86378
Out Of Memory errors in Integrity Lifecycle Manger logs should provide more useful information
Modified: 25-Aug-2018
Applies To
- PTC RV&S (formerly Integrity Lifecycle Manager) 2009 to 11.1
Description
- Out Of Memory errors in Integrity should provide more useful information
- Java Heap Space error does not distinguish between client or the server
-
Error thrown in client log:
GENERAL(0) mks.frame.app.commands.CommandPanicException: mks.frame.app.commands.CommandPanicException: MKS124804: Internal error detected: Error was: mks.frame.exception.OutOfMemoryApplicationError: Not enough memory: The application ran out of memory on the client or server.at mks.frame.app.commands.Command.<clinit>(Command.java:125)at java.lang.Class.forName0(Native Method)at java.lang.Class.forName(Class.java:190)at mks.util.ObjectCreator.getClass(ObjectCreator.java:260)at mks.util.ObjectCreator.createObject(ObjectCreator.java:62)at mks.frame.app.ui.Interactor.createCommand(Interactor.java:50)at mks.frame.app.ui.cli.CliInteractor.runCommand(CliInteractor.java:203)at mks.frame.app.ui.cli.CliCommandRunner.runCommand(CliCommandRunner.java:62)at mks.frame.app.ui.SuspendableCommandRunner.run(SuspendableCommandRunner.java:398)at java.lang.Thread.run(Thread.java:724)
This is a printer-friendly version of Article 86378 and may be out of date. For the latest version click CS86378