Hello, I need your help in getting to the bottom of a memory issue we are facing.
We are running EJB based applications on Web Logic Server (WLS) 6.1 SP2 on Solaris 8 servers using 1.3.1_03 JDK. There are several applications running, but lets use one of them as example. I am using the following JDK parameters: -XX:NewSize=96m -XX:MaxNewSize=96m -Xms384m -Xmx384m -XX:SurvivorRatio=2 The memory values on Solaris, before the application is started, are as follows: Real memory = 4096M, Free memory = 2415M, Swap in use = 1059M, Swap free = 2322M When I start the application, I can see the memory foot print for the application at around 540 Meg. Since JVM pre-allocates heap space, I expect this number to remain constant as the application is stressed. But this does not happen, and it puzzles me. I see the memory footprint of application go up, and that makes me believe that is a memory leak somewhere. Since heap space remains below the selected limit (384M), and the application does not over-run heap, it makes me believe that the memory leak is not happening in application code; rather it is Web Logic Server that is leaking memory. As the application runs, the memory footprint increase from 540M to almost 900M, to the point the system is left with very low free swap space, and the application (not necessarily this particular one) starts throwing OutOfMemoryError. At this point, it becomes impossible to recover and the only way out is to bounce WLS. Does it sound like a memory leak issue to you ? Do you agree that it look like a WLS memory leak? If anybody had similar experience, please help me with your advice. I would be very interested in knowing how you diagnosed the problem and what solution did you apply. Thanks, Asad Faizi =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
