Bug #41438 | Tomcat java process uses too much memory | ||
---|---|---|---|
Submitted: | 12 Dec 2008 15:54 | Modified: | 21 Jul 2009 13:36 |
Reporter: | Diego Medina | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Server | Severity: | S2 (Serious) |
Version: | 2.0.1.7125 | OS: | Any (java 1.6) |
Assigned to: | MC Brown | CPU Architecture: | Any |
[12 Dec 2008 15:54]
Diego Medina
[12 Dec 2008 17:26]
Diego Medina
Going to the Dashboard->Settings->Product info I see JVM Max 545.81 MB JVM Total 545.81 MB It respects the values from -Xmx
[12 Dec 2008 17:43]
Diego Medina
Both agents are using ssl
[14 Dec 2008 4:26]
Diego Medina
Running the service manager on the same laptop but using java 1.5 does not show this problem.
[16 Dec 2008 17:02]
Gary Whizin
We limit heap to 768 MB, how is it using 2 GBs? It probably is related to SSL, but... What happens without using SSL? And then look at Apple bug db to see if java memory usage is a known problem...
[17 Dec 2008 16:47]
Sloan Childers
We should also take a look at the process parameter list and make sure we are not specifying multiple memory settings. This was discovered on one of the support servers recently and had the same behavior. Possibly the 1.6 JVM ignores the memory setting if multiple are set whereas the 1.5 JVM just took the first.
[18 Dec 2008 16:12]
Diego Medina
We pass twice the -Xmx parameters, I'll start the service manager using just one of them and see if I can see the same memory problem.
[18 Dec 2008 20:19]
Mark Leith
I'm seeing this on a linux 64bit server as well. Uploading a file with some memory stats from the OS on the Java process.
[19 Dec 2008 21:40]
Diego Medina
passing only one -Xmx value does not prevent this problem
[7 May 2009 15:19]
Sloan Childers
Has this been resolved by the recent performance/memory work Oldag has been concentrating on?
[18 May 2009 13:49]
Diego Medina
Verified fixed in 2.1.0.1039
[21 Jul 2009 13:36]
Tony Bedford
An entry was added to the 2.1.0 changelog: Running the Service Manager on Mac OS X and monitoring two servers with two agents for at least 16 hours caused the Java process to use 2.08 GB of memory.