Bug #40215 Incorrect setting for HeapDumpPath when installing Service Manager

• Submitted: 21 Oct 2008 16:18
• Modified: 11 Nov 2008 15:36
• Reporter: Andy Bang
• Status: Closed
• Category: MySQL Enterprise Monitor: Installing
• Severity: S3 (Non-critical)
• Version: 2.0.0.7078
• OS: Any
• Assigned to: BitRock Merlin
• CPU Architecture: Any

[21 Oct 2008 16:18] Andy Bang

Description:
On Windows we have (in mysqlmonitorctl.bat):

@@BITROCK_TOMCAT_ROOTDIR@@\bin\tomcat6.exe" //US//MySQLEnterpriseTomcat ++JvmOptions="-XX:HeapDumpPath=@@BITROCK_TOMCAT_ROOTDIR@@\temp

But on other platforms we have (in catalina.sh):

JAVA_OPTS="$JAVA_OPTS -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -server"

The path should be the same on all platforms.  Note that /tmp is in-memory on solaris.

How to repeat:
See above.

Suggested fix:
Set the path to @@BITROCK_TOMCAT_ROOTDIR@@\tmp on Windows (i.e. temp->tmp).

Set the path to @@BITROCK_TOMCAT_ROOTDIR@@/tmp on all other platforms.

[22 Oct 2008 15:51] BitRock Merlin

Patch sent to Keith.

[22 Oct 2008 21:56] Keith Russell

Patch applied in versions +> 2.0.0.7083.

[7 Nov 2008 23:45] Marcos Palacios

Verified fixed in bld 2.0.0.7092.

[11 Nov 2008 15:36] Tony Bedford

An entry was added to the 2.0 changelog:

The Service Manager installer set the Java Virtual Machine option HeapDumpPath to <install_root>\temp on Windows and /tmp on other platforms. For consistency the HeapDumpPath directory should have been set to <install_root>\tmp on Windows.