[nhibernate-issues] [NHJIRA] Commented: (NH-2755) LockMode hash differs in x86 and 64bit OS

[Fabio M. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21252#action_21252 ] 

Fabio Maulo commented on NH-2755:
---------------------------------

Well... that is not the only one place where NH store the hash code at ctor.

> LockMode hash differs in x86 and 64bit OS
> -----------------------------------------
>
>                 Key: NH-2755
>                 URL: http://216.121.112.228/browse/NH-2755
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.2.0Beta2
>            Reporter: Anton
>            Priority: Major
>
> When using LockMode over remoting between PCs with x86 and 64bit operating systems there is different result in GetHashCode.
> It leads to error "LockMode Upgrade not supported by NHibernate.Persister.Entity.SingleTableEntityPersister " when I pass LockMode.Upgrade from x86 to 64bit to do
> session.Lock(this, lockMode)
> It is caused by generating and storing hash code upon creating instance of LockMode.
> LockMode constructor uses a XOR (^) operand to generate and store hash code, and it has different behavior depends on OS type (x84, 64bit)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira