[ https://issues.apache.org/jira/browse/CLOUDSTACK-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029257#comment-14029257 ]
Adrian Lewis commented on CLOUDSTACK-6892: ------------------------------------------ Added in 4.4 and Future as I assume this hasn't been picked up already. > Database HA Config prevents mgmt server from starting > ----------------------------------------------------- > > Key: CLOUDSTACK-6892 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6892 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup, Management Server > Affects Versions: Future, 4.3.0, 4.4.0 > Environment: MySQL configured for DB HA > Reporter: Adrian Lewis > Priority: Critical > > When configuring the database HA feature introduced in 4.3, the manangement > server fails to create the DB connection due to the mysql connector jar being > loaded using tomcat's common class loader but the > "cloud-plugin-database-mysqlha-4.3.0.jar" is loaded by the webapp class > loader. > The cloud-plugin-database-mysqlha-4.3.0.jar needs to also be loaded from the > common class loader instead of webapp class loader. > Fix is to declare the cloud-plugin-database-mysqlha-4.3.0.jar under the > common.loader section in /etc/cloudstack/management/catalina.properties. > Only tested using a fresh install on Centos 6.5 and the public repo packages. > Manual fix provided by Damoder Reddy in users mailing list: "Looks like we > did not change the catalina.properties while refactoring out the mysql > connector part" -- This message was sent by Atlassian JIRA (v6.2#6252)