[
https://issues.apache.org/jira/browse/CLOUDSTACK-10195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael Weingärtner updated CLOUDSTACK-10195:
--------------------------------------------
Description:
When using CloudStack with database HA configuration user receives warnings
constantly saying “No database selected”.
This problem happens at
com.cloud.cluster.ClusterManagerImpl.getHeartbeatTask().new
ManagedContextRunnable() {...}.runInContext(), line 550. The scheme of the
database is not properly set in the transaction when database HA options are
enabled.
was:
When using CloudStack with database HA configuration user receives warnings
constantly saying “No database selected”.
This problem happens at
com.cloud.cluster.ClusterManagerImpl.getHeartbeatTask().new
ManagedContextRunnable() {...}.runInContext(), line 550. The scheme of the
database is not properly set in the transaction when database HA options are
enabled. The solution is to use
txn.transitToAutoManagedConnection(TransactionLegacy.CLOUD_DB);
> CloudStack MySQL HA problem -- No database selected
> ---------------------------------------------------
>
> Key: CLOUDSTACK-10195
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10195
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.9.0, 4.9.2.0, 4.9.3.0
> Reporter: Rafael Weingärtner
> Assignee: Rafael Weingärtner
> Priority: Minor
>
> When using CloudStack with database HA configuration user receives warnings
> constantly saying “No database selected”.
> This problem happens at
> com.cloud.cluster.ClusterManagerImpl.getHeartbeatTask().new
> ManagedContextRunnable() {...}.runInContext(), line 550. The scheme of the
> database is not properly set in the transaction when database HA options are
> enabled.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
