Even as Jetty stops deploying and then redeploys your web application, the static reference persists, so the object cannot be cleared from memory. Static fields are started with the classloader’s value.There are two types of leaks in this case: daemon threads and static fields. #JPROFILER MEMORY LEAK CODE#When your code keeps referring to a WebApp classloader, memory leaks can easily happen. or higher, you can prevent WebApp classloader pinning. Avoid memory leaks related to a WebApp classloader WeakReference objects, especially with a cleanup thread, can help you avoid memory errors. Using reference objects, you can work with the garbage collector to automate the task of removing listeners that are weakly reachable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |