Bug #50368 document configuring tomcat memory usage on Windows
Submitted: 15 Jan 2010 14:12 Modified: 20 Jan 2010 16:19
Reporter: Andrii Nikitin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Documentation Severity:S3 (Non-critical)
Version:1.3,2.0,2.1,2.2 OS:Windows
Assigned to: MC Brown CPU Architecture:Any

[15 Jan 2010 14:12] Andrii Nikitin
Description:
related to bug #48485

changing setenv.bat didn't work for me, probably because Window Service should be configured differently.

How to repeat:
see documentation

Suggested fix:
Not sure which actions are correct.

Following items worked once but they probably will not survive MEM upgrade:

1. open following file in text editor:
"C:\Program Files (x86)\MySQL\Enterprise\Monitor\mysqlmonitorctl.bat"

2. Append "--JvmMs=1024 --JvmMx=1024" with new values to line #61, so it will look like:

"C:\PROGRA~2\MySQL\ENTERP~1\Monitor\apache-tomcat\bin\tomcat6.exe" //US//MySQLEnterpriseTomcat --Jvm="C:\Program Files (x86)\MySQL\Enterprise\Monitor\java\bin\server\jvm.dll" --JvmMs=1024 --JvmMx=1024

3. Save file
4. run

cd "C:\Program Files (x86)\MySQL\Enterprise\Monitor"
mysqlmonitorctl.bat uninstall
mysqlmonitorctl.bat install
mysqlmonitorctl.bat start

Anyway correct way should be described in manual
[20 Jan 2010 11:22] BitRock Merlin
The correct approach to change the JAVA_OPTS is the following:

1. Modify the JAVA_OPTS the <installdir/apache-tomcat/bin/setenv.bat file. This file will be preserved during the upgrade.

2. Reinstall the service. You can reinstall the service using the "mysqlmonitorctl.bat [uninstall | install]" from the Administrator command prompt or you can use the MySQL Enterprise Monitor service shortcuts.

3. You can check the new JAVA_OPTS in the following Windows registry:

My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\MySQLEnterpriseTomcat\Parameters\Java 

Or you can also check them in the Monitor application:

http://localhost:18080/ProductInfo.action
[20 Jan 2010 16:19] MC Brown
The documentation has been updated with these instructions, including the note about reetention over upgrades.