JVM Memory Utilization HighIssue Observing JVM Memory Utilization High and seeing below errors com.glide.sys.TransactionCancelledException: Transaction cancelled: Available memory is almost depletedat com.glide.sys.Transaction.cancelIfRequested(Transaction.java:1652)at com.glide.sys.Transaction.cancelIfNecessary(Transaction.java:1767)at com.glide.sys.TransactionManager.cancelIfNecessary(TransactionManager.java:68)at com.glide.sys.TransactionManager.run(TransactionManager.java:188)at org.mozilla.javascript.Context.cancellationCheck(Context.java:3417)at org.mozilla.javascript.ContextFactory.observeInstructionCount(ContextFactory.java:608)at org.mozilla.javascript.Context.observeInstructionCount(Context.java:2608)at org.mozilla.javascript.Interpreter.addInstructionCount(Interpreter.java:3251)at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:2059)at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:830)at org.mozilla.javascript.InterpretedFunction.lambda$call$0(InterpretedFunction.java:160)at com.glide.caller.gen.sys_rte_eb_entity_mapping_f460dd10c3363110cff9f1067d40dd52_condition_script.call(Unknown Source)at com.glide.script.ScriptCaller.call(ScriptCaller.java:18)at org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:159)at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:597)at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3573)at org.mozilla.javascript.InterpretedFunction.exec(InterpretedFunction.java:172)at com.glide.script.ScriptEvaluator.execute(ScriptEvaluator.java:416)at com.glide.script.ScriptEvaluator.evaluateString(ScriptEvaluator.java:228)at com.glide.script.ScriptEvaluator.evaluateString(ScriptEvaluator.java:143)at com.glide.script.fencing.GlideScopedEvaluator.evaluateScript(GlideScopedEvaluator.java:348)at com.glide.script.fencing.GlideScopedEvaluator.evaluateScript(GlideScopedEvaluator.java:240)at com.glide.script.fencing.GlideScopedEvaluator.evaluateScript(GlideScopedEvaluator.java:219)at com.glide.robust_transform_engine.RobustTransformEngine.transformRteInputs(RobustTransformEngine.java:255)at com.glide.db.impex.transformer.service.RobustImportSetProcessor.sendToRobustTransformEngine(RobustImportSetProcessor.java:137)at com.glide.db.impex.transformer.service.RobustImportSetProcessor.processBatch(RobustImportSetProcessor.java:118)at com.glide.db.impex.transformer.service.RobustImportSetProcessor.transform(RobustImportSetProcessor.java:83)at com.glide.system_import_set.ImportSetTransformerImpl.doRobustImportSetTransform(ImportSetTransformerImpl.java:166)at com.glide.system_import_set.ImportSetTransformerImpl.transformAllMaps(ImportSetTransformerImpl.java:114)at com.glide.system_import_set.ImportSetTransformer.transformAllMaps(ImportSetTransformer.java:91)at com.snc.automation.ImportSetTransformerJob.runTransform(ImportSetTransformerJob.java:267)at com.snc.automation.ImportSetTransformerJob.execute(ImportSetTransformerJob.java:101)at com.glide.schedule.JobExecutor.lambda$executeJob$0(JobExecutor.java:140)at com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:143)at com.glide.schedule.JobExecutor.execute(JobExecutor.java:127)at com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:338)at com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$0(SchedulerWorkerThread.java:225)at com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)at com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:225)at com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:101)CauseFor each asset, we will be fetching associated software data. In this case, assets have related software data and fetching for each asset exceeds the response size.ResolutionThe issue is idenitfied as problem. We already have raised a problem for this issue. Problem PRB1784719 -->Below is the link:https://support.servicenow.com/nav_to.do?uri=%2Fproblem.do%3Fsys_id%3D5294284f97fd8e9424a7739c1253afa2%26sysparm_view%3D%26sysparm_domain%3Dnull%26sysparm_domain_scope%3Dnull) to address this defect.-->We will fix this issue in future releases. You can subscribe to Problem for more updates.