cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-10195) CloudStack MySQL HA problem -- No database selected
Date Mon, 18 Dec 2017 18:37:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-10195:

rafaelweingartner commented on issue #2364: [CLOUDSTACK-10195] CloudStack MySQL HA problem
-- No database selected
   Because it was testing the method   `txn.transitToUserManagedConnection(getHeartbeatConnection())`.
   I replaced the use of this method by `txn.transitToAutoManagedConnection(TransactionLegacy.CLOUD_DB);`
   If you see in that code at line 600, after "trying" to reuse a connection if something
goes wrong, it will try to transit to a transaction using schema "Cloud_DB", and then it will
close the transaction. The only place where the transaction was "reused" is there. So, when
I changed `txn.transitToUserManagedConnection(getHeartbeatConnection())` to `txn.transitToAutoManagedConnection(TransactionLegacy.CLOUD_DB);`,
the first method could be deleted. After that, I inspected and this method is not used anywhere
else. Therefore, I also removed the method and its test cases.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> CloudStack MySQL HA problem -- No database selected
> ---------------------------------------------------
>                 Key: CLOUDSTACK-10195
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.9.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 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

View raw message