Hello,
I would update my previous article concerning a solution in order to avoid the famous OutOfMemoryError: Java heap space or OutOfMemoryError: PermGen space errors.
This error java.lang.OutOfMemoryError in Java is a subclass of java.lang.VirtualMachineError which is thrown by the Java Virtual Machine when it ran out of memory in heap or it cannot allocate an object because it is out of memory, and no more memory could be made available by the garbage collector, for example:
- when not enough memory can be allocated for a new array;
- when not enough memory is available for your class to load;
- when too many threads / not enough stack space available for a new thread.
However, it is possible to avoid this error by verifying the memory status of JVM. So, we have created a simple technical component Memory Checker whose the role is to check the available memory space in VM for the execution of Java code in order to avoid these “out of memory” errors. If there is enough memory, the current thread will be put on hold for the specified delay (between 2 retries).
As a reminder:
- PermGen is the memory dedicated to the permanent objects in the VM (Class names, internalized strings, objects that will never get garbage-collected). So the -XX:PermSize=128M parameter corresponds to the memory reserved at the application server starting time. The -XX:MaxPermSize parameter corresponds to the maximum memory usable by the server before swaping.
- -Xms1024m corresponds to the memory reserved at the application server starting time for the non permanent (volatile) objects in the VM.
- -Xmx4096m corresponds to the maximum memory usable by the server for the non permanent (volatile) objects in the VM, if this limit is reached, the server persists the data on disk via swaping.
…so, at the application server starting time, the memory reserved will be the total of -XX:PermSize and -Xms parameters.
I. Memory Checker
So, we will create a class named MemoryChecker:
01 | public class MemoryChecker { |
04 | private static int NB_OF_RETRY = 5; |
09 | private static int WAITING_DELAY_MS = 500; |
…this class will contain a private static method logMemoryStatusInConsole which will print the memory status in console, eg the total amount of memory in the JVM, the maximum amount of memory that the JVM will attempt to use and the amount of free memory in the JVM:
02 | * Print the memory status in console |
05 | private static void logMemoryStatusInConsole(String threadName){ |
15 | Runtime rt = Runtime.getRuntime(); |
19 | long totalNow = rt.totalMemory(); |
23 | long maxPossible = rt.maxMemory(); |
26 | long freeNow = rt.freeMemory(); |
28 | long usedNow = totalNow - freeNow; |
29 | long freeRealPossible = maxPossible - usedNow; |
32 | System.out.println(threadName + " : " + "memorybroker : free "+ freeRealPossible/1024 + "ko : (total/max) " + totalNow/1024 + "ko/" + maxPossible/1024+"ko"); |
…this class will contain a public static method checkMemoryAndIfNecessaryPutThreadOnHold which will check if there is enough memory to process the given number of bytes. If there is enough memory, the current thread will be put on hold for the specified delay.
02 | int nbLoop = NB_OF_RETRY; |
05 | long freeNow = Runtime.getRuntime().freeMemory(); |
06 | long totalNow = Runtime.getRuntime().totalMemory(); |
07 | long maxPossible = Runtime.getRuntime().maxMemory(); |
08 | long usedNow = totalNow - freeNow; |
09 | long freeRealPossible = maxPossible - usedNow; |
11 | if(freeRealPossible >= memorySize){ |
16 | System.out.println(threadName + " : " + memorySize/1024 + "ko : Not enough memory for the current thread, try again in " + WAITING_DELAY_MS + " ms"); |
19 | Thread.sleep(WAITING_DELAY_MS); |
28 | System.out.println(threadName + " : " + memorySize/1024 + "ko : Not enough memory for the current thread despite testing, so the propagation of OutOfMemoryError will be done."); |
30 | logMemoryStatusInConsole(threadName); |
31 | throw new OutOfMemoryError(); |
II. Test Memory Checker
We will create a main method in order to simulate multiple threads which call load a file (size of bytes) into memory Java (JVM):
05 | final int memorySizeNeeded = 300000*1024; |
08 | ExecutorService exec = Executors.newFixedThreadPool(nbThreads); |
09 | for (int i = 0; i < nbThreads; i++) { |
12 | Runnable runnable = new Runnable(){ |
13 | private String threadName = null; |
15 | this.threadName = "thread_"+valueI; |
18 | System.out.println(threadName + ":-- START --"); |
21 | System.out.println(threadName + " : " + "Memory status before the memory checking"); |
22 | logMemoryStatusInConsole(threadName); |
27 | checkMemoryAndIfNecessaryPutThreadOnHold(memorySizeNeeded, threadName); |
29 | byte[] tab = new byte[memorySizeNeeded]; |
32 | logMemoryStatusInConsole(threadName); |
33 | System.out.println(threadName + ":-- END --"); |
36 | System.out.println(threadName + ":-- ERROR --" + th); |
41 | exec.submit(runnable); |
Test n°1
With 2 threads and a 300Mo for the memory needed fo each thread:
5 | final int memorySizeNeeded = 300000*1024; |
… results: there is not enough of memory for all 2 threads, so, an error OutOfMemoryError is thrown:
03 | thread_1 : Memory status before the memory checking |
04 | thread_1 : memorybroker : free 252893ko : (total/max) 15872ko/253440ko |
05 | thread_1 : 300000ko : Not enough memory for the current thread, try again in 500 ms |
06 | thread_0 : Memory status before the memory checking |
07 | thread_0 : memorybroker : free 252893ko : (total/max) 15872ko/253440ko |
08 | thread_0 : 300000ko : Not enough memory for the current thread, try again in 500 ms |
09 | thread_1 : 300000ko : Not enough memory for the current thread, try again in 500 ms |
10 | thread_0 : 300000ko : Not enough memory for the current thread, try again in 500 ms |
11 | thread_1 : 300000ko : Not enough memory for the current thread, try again in 500 ms |
12 | thread_0 : 300000ko : Not enough memory for the current thread, try again in 500 ms |
13 | thread_1 : 300000ko : Not enough memory for the current thread, try again in 500 ms |
14 | thread_0 : 300000ko : Not enough memory for the current thread, try again in 500 ms |
15 | thread_1 : 300000ko : Not enough memory for the current thread, try again in 500 ms |
16 | thread_0 : 300000ko : Not enough memory for the current thread, try again in 500 ms |
17 | thread_1 : 300000ko : Not enough memory for the current thread despite testing, so the propagation of OutOfMemoryError will be done. |
18 | thread_1 : memorybroker : free 252893ko : (total/max) 15872ko/253440ko |
19 | thread_0 : 300000ko : Not enough memory for the current thread despite testing, so the propagation of OutOfMemoryError will be done. |
20 | thread_0 : memorybroker : free 252893ko : (total/max) 15872ko/253440ko |
21 | thread_0:-- ERROR --java.lang.OutOfMemoryError |
22 | thread_1:-- ERROR --java.lang.OutOfMemoryError |
Test n°2
With 2 threads and a 300ko for the memory needed fo each thread:
5 | final int memorySizeNeeded = 300*1024; |
… results: there is enough of memory for all 2 threads, so, no error OutOfMemoryError thrown:
03 | thread_1 : Memory status before the memory checking |
04 | thread_1 : memorybroker : free 252893ko : (total/max) 15872ko/253440ko |
05 | thread_1 : memorybroker : free 252593ko : (total/max) 15872ko/253440ko |
07 | thread_0 : Memory status before the memory checking |
08 | thread_0 : memorybroker : free 252593ko : (total/max) 15872ko/253440ko |
09 | thread_0 : memorybroker : free 252293ko : (total/max) 15872ko/253440ko |
III. Conclusion
This MemoryChecker class must be used for sensitive areas of an application (created thread pool, webservices, servlets, file handling…). These “sensitive” points can be targeted via tools like jconsole and visualvm that monitor the activity (eg total number of thread) of JVM on the real-time, which can be a big help.
But, the number of threads in a JVM is not infinitely expandable, so, if the application needs a very large number of thread to meet demand, several options should be considered:
- First solution: the least expensive change, modify (if possible) the Xmx (and/or Xss) parameters of your server in order to may create more threads. Then, it is well advised to re-test your application.
- Second solution: modify the physical and/or logical architecture of your application:
- If you are on 32bit machines, switch to 64 bits, so as to extend the size limit of the process;
- Modify your application so that you can add more instances of the JVM. Make the application more scaleable horizontally;
- Turn (if possible) your synchronous processes into asynchronous processes in order to better manage your resources and minimize your wait time threads.
Source: MemoryChecker.java
That’s all!!!
Huseyin OZVEREN
Related
