We sometimes see out-of-memory problems with iACS 5250 start-up while running on Windows Terminal Server. It's always caused by the Windows VM starving for RAM. Being a Java app, iACS has to start a JVM for each Windows desktop session.
From: Smith, Mike [mailto:Mike_Smith@xxxxxxxxxxxxxxxx]
Sent: Wednesday, January 15, 2020 3:24 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Access Client Solutions - Locking
We are using ACS 22.214.171.124 in a Citrix Xen Virtual Desktop Environment.
* Citrix XenDesktop 7.15 LTSB using Machine Creation Services
* Hypervisor: VMWare ESXi 6.5
* VMWare Tools version (current): 10305
* OS: Windows 10 LTSC (Current on Windows Critical and Security Updates)
* RAM: 8GB
* DISK: 70GB
* Processor: 2 CPU
* Java version: 8.241 (as of today) previously 8.31
We are starting to have a number of users when they start up a 5250 session from ACS, the Session will freeze/lockup. Looking into it at this point we are seeing very high memory usage If we can get the session closed and then reopen it, sometimes it clears itself up and other times it doesn't.
Any having any similar issues? Things we can check or do to remediate?
NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.