cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sadhu suresh (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-4095) Region id within the Database Transaction code...
Date Mon, 11 Nov 2013 12:45:42 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

sadhu suresh closed CLOUDSTACK-4095.
------------------------------------


verified the issue by updating the  region id as 20  and deploy db with -r option and default
region id set as 20 .so its working fine so closing issue.

> Region id within the Database Transaction code...
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-4095
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4095
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Alex Huang
>            Assignee: Kishan Kavala
>            Priority: Critical
>             Fix For: 4.2.1
>
>
> Why should the region id be in Transaction Id and then propagated through GenericDao.
 This is should not happen at all.  We need to fix this.  GenericDao is a generic framework.
 It should not understand regions at all.  Even if you're using the db.properties to expose
region id, you can read it yourself in your code, rather than pushing it into Transaction.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message