Bug #53568 https stops working if tomcat native is installed
Submitted: 11 May 2010 14:45 Modified: 8 Apr 2011 15:18
Reporter: Roger David Nay Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Installing Severity:S2 (Serious)
Version:2.2.0.1709 OS:Any
Assigned to: BitRock Merlin CPU Architecture:Any

[11 May 2010 14:45] Roger David Nay 
Description:
We use tomcat-native rpm (centos 5).

With 2.2 merlin (this seemed to be an issue too with 2.1) we now see a different behaviour, if the tomcat-native rpm is installed on the server, https stops working. This is without changing configuration of merlin at all.

How to repeat:
N/A

Suggested fix:
Allow us to use native tomcat installation.
[11 May 2010 16:11] Enterprise Tools JIRA Robot 
Andy Bang writes: 
BitRock,

Customer had installed native Tomcat libraries and had everything working with those. After upgrade, it wasn't working. Removing the native libs fixed the problem (in the sense that Merlin was working again), but customer would prefer to use the native libs. We presume the problem was the result of overwriting something in server.xml. If so, is this something you can preserve?
[11 May 2010 17:18] BitRock Merlin 
The current upgrade approach is to maintain the previous server.xml file and modify the ports using xpath, so the custom changes should be preserved.
[13 May 2010 7:45] Simon Mudd 
I'm not sure the issue is about upgrading or not. I think it's simply about installing tomcat-native or removing it. Previously on this box installing tomcat-native "used to work". That is the merlin dashboard worked and we got better SSL performance. Now with tomcat-native installed https access fails. Logging is not clear. Removing the rpm again makes it work.

The problem may be the rpm, it may be the version of tomcat. I'm really not sure, especially as the problem is on our "secondary" tomcat instance. Our main one seems to be configured the same way and still works with tomcat-native installed.

However, our primary dashboard version is still running 2.1.2.1158 and has not been upgraded yet, so the versions are not currently the same.
[31 Jan 2011 23:02] Enterprise Tools JIRA Robot 
Marcos Palacios writes: 
Build 2.3.2.2052 has a problem on some platforms, see EM-3816.
[8 Apr 2011 15:18] Marcos Palacios 
Verified fixed in Monitor build 2.3.2.2055.