Increasing Java Memory Limits

Chronicall/ACR 3.10 and above

Please note, the following steps are for v.3.10 and above, as these newer versions have Java 64-bit built-in, so their RAM allocations can go higher (unless you are Shoretel/Mitel based, which is limited to 32-bit)

Windows

1. Navigate to the tomcat/bin/app folder in the Chronicall/ACR directory
   
   • Default locations

     • C:\Program Files (x86)\Xima Software\Chronicall\bin\app

     • C:\Program Files\Chronicall\bin\app

     • C:\Program Files\Avaya Call Reporting\bin\app

2. Right-click and run ChronicallServerw.exe as an Administrator
3. Click the Java tab

   • Java's "Initial memory pool" and "Maximum memory pool" are listed at the bottom

     • We always leave the Initial memory pool to its default value
     • Most new installs will default to Maximum memory pool of 384, and this can be increased, and is recommended to increase it in multiples of 1024 (1024, 2048, 3072, 4096, etc)

   • NOTE: 32-bit versions of Chronicall (Shoretel/Mitel and 32 bit Chronicall installs) have a "Maximum memory pool" value of 1024 MB
     
     
     
     

4. Adjust your "Maximum memory pool" up to the amount you need.  It is recommended that you add RAM in multiples of 1024 MB.  So if you have 2 GB free on the server, you could set your Maximum memory pool to 2048 (2 x 1024)

   • Make sure your server has the available RAM resources before making this change.  You don't want to tell Chronicall to use more RAM than the server has available

5. You will need to restart Chronicall\ACR before your changes will take effect

Linux

1. Navigate to the tomcat/bin/app folder in the Chronicall/ACR directory
   • Default locations
     • /var/lib/Xima Software/Chronicall/bin/app
     • /var/lib/Chronicall/bin/app
     • /var/lib/Avaya Call Reporting/bin/app
2. Open the ChronicallServer.cfg file
3. Edit the -Xmx4g line to the correct amount of RAM you wish to allocate
   • NOTE: Your amount of initial RAM allocation may be different
   • NOTE: -Xmx4g is equal to 4 GB of RAM, -Xmx256m is equal to 256 MB of RAM
   • Make sure your server has the available RAM resources before making this change
     
     
     
     
4. Save the changed file
5. Restart Chronicall/ACR services for this to go into effect

Chronicall 3.9.4 and earlier

Please note that the following steps are for v.3.9.4 and earlier, as the newer versions have Java 64-bit built-in, so their allocations can go higher. If you are on an earlier version of Chronicall and would like to upgrade to 64-bit Java, you can follow this article to upgrade Java to 64-bit.  This will allow you to allocate more than 1024 MB of memory.

Windows

1. Navigate to the tomcat/bin folder in the Chronicall directory

   • Default location

     • C:\Program Files (x86)\Xima Software\Chronicall\tomcat\bin\

2. Right-click and run chronicallw.exe or ChronicallServerw.exe as an Administrator

3. Click the Java tab

   • Java's "Initial memory pool" and "Maximum memory pool" are listed at the bottom

   • NOTE: 32-bit Chronicall/Java has a "Maximum memory pool" value of 1024 MB

     
     
     

4. Adjust your "Maximum memory pool" up to the amount you need

   • Make sure your server has the available RAM resources before making this change

5. You will need to restart Chronicall before your changes will take effect

Linux

To increase Java's memory limit on a Linux Chronicall server we need to download and edit the setenv.sh file in the tomcat/bin folder.

1. If you have not made any prior modifications, simply open a command terminal and go through the following steps

   • NOTE: This will stop and restart the Chronicall service

2. Gain root access to the server either with

   • su root

     • or

   • sudo su

3. Enter your root password
4. Stop the Chronicall service

   • service chronicall stop

5. Navigate to the tomcat/bin file in the Chronicall directory

   • Default location

     • /var/lib/Xima\ Software/Chronicall/tomcat/bin

6. Run the following command to pull in the setenv.sh file

   • wget ftp://media.ximasoftware.com/ChronicallLinux/setenv.sh

7. Turn the file into an executable with this command: 

   • chmod +x setenv.sh

8. Start the Chronicall service back up again

   • service chronicall start

9. If you have made prior modifications such as an alternate Java JRE, then add the following line to the setenv.sh file

10. export JAVA_OPTS="$JAVA_OPTS -Xms512m -Xmx512m"

    • You can modify the "512m" as needed, for example:

      • export JAVA_OPTS="$JAVA_OPTS -Xms256m -Xmx1024m"

Web Client (Windows)

If you experience performance issues while using the Chronicall Web client, you may be able to solve them by allowing Java to use more RAM.

1. Navigate to Java in the Control Panel menu of Windows

2. Under the Java tab, click "View..."
   
   

   
   
   

3. This will open the Java Runtime Environment Settings window

   • Your current version of Java will be listed in the "Product" column

4. Double-click the "Runtime Parameters" field and enter:

   •  -Xmx400m

     • NOTE: You can replace 400 with the number of megabytes you want Java to be able to use.

   • Make sure your computer has the available RAM resources before making this change

      

     
     
     

5. Click "OK" to save your changes
6. Before your changes will take effect, you will need to restart your web browser.