You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Nitin Mehta (JIRA)" <ji...@apache.org> on 2013/07/01 16:15:20 UTC

[jira] [Resolved] (CLOUDSTACK-3039) Failed to attach volumes for clusters with id > 127

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

Nitin Mehta resolved CLOUDSTACK-3039.
-------------------------------------

    Resolution: Fixed
      Assignee: Nitin Mehta

With the object store code checked in, dont need to check this any more.
                
> Failed to attach volumes for clusters with id > 127
> ---------------------------------------------------
>
>                 Key: CLOUDSTACK-3039
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3039
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Nitin Mehta
>            Assignee: Nitin Mehta
>             Fix For: 4.2.0
>
>
> Failed to attach volumes for clusters with id > 128 
> The reason is because we use Java == than the equals for comparing Long object. This operation works till 127 because of JVM optimization where it precreates objects from -127 to 128 and passes the same reference instead of creating a new instance every time

--
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