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

Prasanna Santhanam resolved CLOUDSTACK-1856.
--------------------------------------------

    Resolution: Not A Problem

Those properties are not invoked by any part of our database/transaction code 
and not used anywhere by CloudStack. removed them using following patch.

commit 988ccfc45d8a4f7b689a75adc76c06f0ec1a06db
Author: Laszlo Hornyak <lhorn...@redhat.com>
Date:   Sun Nov 11 22:06:08 2012 +0100

    removed some unused database connection properties
    
    Signed-off-by: Laszlo Hornyak <lhorn...@redhat.com>
    Signed-off-by: Prasanna Santhanam <t...@apache.org>

                
> Upgrade 4.0 -> 4.1 - Fresh install of  4.1 has 3 parameters missing in 
> db.properties compared to an upgrdaed 4.0 set up. 
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1856
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1856
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0
>         Environment: Upgrade 4.0 -> 4.1 
>            Reporter: Sangeetha Hariharan
>            Assignee: Prasanna Santhanam
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Upgrade 4.0 -> 4.1 - Fresh install of  4.1 has 3 parameters missing in 
> db.properties compared to an upgrdaed 4.0 set up
> Compare the "db.cloud.*" parameters in db.properties of a fresh install of 
> 4.1 and a 4.1 set up that was upgraded from 4.0
> I see the following parameter in a upgraded 4.1 set up that are not present 
> in fresh 4.1 set up:
> db.cloud.removeAbandoned=false
> db.cloud.removeAbandonedTimeout=300
> db.cloud.logAbandoned=true

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to