At our hospital we are using two version of the MIPS Glims laboratory software.
Glims 8 is being used in one department. Another department has just upgraded to Glims 9.
Thinapp packages have been made with Thinapp 5.1.0-2079447
In both cases, the Thinapp packages keep hanging up intermittantly in use.
There seems to be now specific set of actions performed by users to make the application hangup.
The solution is to kill the app in Task Manager and have the use logout-login. After that the Thinapp works again, usually without problems until the next time.
The packages are run on our VDI-environment, while the GLIMS-servers are also virtualised and have 6 CPU's and enough memory according to MIPS.
The VDI's are running Windows 7 32-bit on 3Gb of memory.
DOT NET 4.5.2 is locally installed.
The Thinapp contains the Progress client as well as Glims. Nothing else.
I have made the following adjustments in the Package.ini
DisableTransactionRegistry=1
SandboxName=RN100209_Glims-MMI_Prod_8.11.10_V01
InventoryName=RN100209_Glims-MMI_Prod_8.11.10_V01
InventoryIcon=%SystemRoot%\Installer\{734BC78E-BFA2-453F-B0BF-1386B6FDDED9}\ARPPRODUCTICON.exe
SandboxPath=%TEMP%
RemoveSandboxOnExit=1
RemoveSandboxOnStart=1
In effect, the Sandbox is now located on the virtual C-drive of the VDI instead of the network (for speed).
It is effectively being emptied at startup and remved on exit as well.
In the progress.ini the following adjustments have been made as well:
MA_JVM_XMS=-Xms128m
MA_JVM_XMX=-Xmx256m
Very often, the thinapp seems to hangup when users are trying to print labels, but this is not always the case.
Has anyone experienced the same problems with Glims and if so, have you found a solution.