LockMode hash differs in x86 and 64bit OS

Description

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)

Environment

None

Activity

Frédéric Delaporte

November 20, 2018 at 10:51 AM

Moved here.

Fabio Maulo

June 1, 2011 at 7:57 AM

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

Anton

June 1, 2011 at 6:44 AM

Yes, LockMode just passes from client to server PC, client is x86, server is 64bit.
When using client 64bit and server 64bit - everything ok.

Stored hashcode in instance of LockMode differs at 86/64

Fabio Maulo

June 1, 2011 at 6:03 AM

What you are doing is pass the NH's LockMode serializaed instance between 2 different machines, right ?

Anton

June 1, 2011 at 5:05 AM

It is in issue description
"LockMode Upgrade not supported by NHibernate.Persister.Entity.SingleTableEntityPersister"

Resize issue view side panel

Fixed

Details

Assignee

Frédéric Delaporte

Reporter

Anton

Priority

Minor

Who's Looking?

Open Who's Looking?

Created June 1, 2011 at 12:34 AM

Updated November 20, 2018 at 10:51 AM

Resolved November 20, 2018 at 10:51 AM

Who's Looking?

LockMode hash differs in x86 and 64bit OS

Description

Environment

Activity

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

Who's Looking?