While in chronicallw.exe, the Maximum Memory Pool can now be increased to 2048MB (or what ever max is required). C:\Program Files\Java\jre1.x.x_xx\bin\server\jvm.dll) and the "Use Default" is unchecked.Ħ. Verify that The Java Virtual Machine field is set to use 64-bit Java (ex. Once updated for the second time navigate to C:\Program Files (x86)\Xima Software\Chronicall\tomcat\bin and run chronicallw.exe as an Administrator. Run the downloaded update.exe one more time.ĥ. If you make Chronicall 64-bit by entering the path in the "Java 64-bit Home" field then the Data Grid will also run 64-bit automatically.Ĥ. Note: If you only want to make the Data Grid run with 64 bit, enter the path to the 64-bit Java in "Data Grid Alternative Java Home".
C:\Program Files\Java\jre1.x.x_xx) and click save. In the "Java 64-bit Home" field enter the path to the 64-bit Java (ex. Once updated, launch Chronicall and go to System Settings > Advanced Settings. (Save the installer, and do not select Run as you will need to run the same update twice).ģ. Once 64-bit Java is installed, update the Chronicall installation to our recommended version. Once downloaded, run the installer to install 64-bit Java.Ģ. Download and save the Windows Offline (64 bit) Java from. The following steps should be completed to allow Chronicall to use 64-bit Java.ġ. If you have 32-bit Java installed, but have not yet increased the memory to see if that helps, instructions on doing that can be found here.
64-bit Java will enable you to give the Chronicall engine or the Data Grid engine memory past the 1024mb limit. Please update to Chronicall 3.12 or later to take advantage of these Java changes.Ĭonfiguring Chronicall to use 64-bit Java may help it to run smoother, especially in environments with large numbers of agents or very high call volume. In Chronicall 3.9.5 and higher, Java was integrated into Chronicall, making this article no longer relevant.
0 kommentar(er)
