![]() ![]() If your application is running, it’s hard to see what objects allocate memory. I was glad to find out it was not a memory leak, but more a warning that the total size of requests could allocate a lot of memory. It turned out that this was related to the amount and type of requests being handled by the application server. You might have guessed it, because only a couple of minutes later we were represented with the OOME message in the server log. Let’s say from 2 Gb the memory footprint went up to 4GB. The web application was running in Tomcat 6 and it appeared that at a certain point in time, the JVM tried to allocate twice the average memory it was using. The situationĪt one of my recent projects we were having some memory related issues on one of the production machines. There are several causes for such an exception, but the most obvious is that there is memory leak somewhere in the application. ![]() The garbage collector inside the JVM will remove most waste, but what happens when not all waste can be removed or something is wrong inside the application? This may result in an exception that probably a lot of developers and system administrators have seen before: (OOME). Most developers working with Java hardly have to think about the memory footprint of their application that they wrote. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |