Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
  b=x4l3W+wDruRaBDJadB5NusY5kZ0nQsY6rEKZMqb/L3KFgl2UWMa3JiZ7oIHas+enN2IHdG8nUPlJ/aBX95BOjQyJ3sf4WMwUpKoiKbx1RPIxpxBB2pynCd4cpjWm2Q8xo/QHrcD/dM1415mxOayxKhgE9LkjoIgFtt7UlM1Knv0=;
Message-ID: <1326322714.50325.YahooMailNeo@web27806.mail.ukl.yahoo.com>
Date: Wed, 11 Jan 2012 22:58:34 +0000 (GMT)
From: Mark Struberg <struberg@yahoo.de>
Reply-To: Mark Struberg <struberg@yahoo.de>
Subject: ManagedCache cache issues?
To: openjpa-dev <dev@openjpa.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

hi!

I'm debugging through a weird bug I have here locally. While doing that I figured that the the cache could suffer from clashes 


ManagedCache.java

StateManagerImpl orig = _main.put(sm.getObjectId(), sm);

the problem is that the same instance of the ManagedCache is being used for different Entities. But for different entities, the ids could be overlapping!

I'm e.g. using
<property name="openjpa.Sequence" value="class-table(Table=SEQUENCES, Increment=20, InitialValue=10000)"/>

Which means that there could be a Customer with id=10001 and an Address with id=10001.
Some query which would touch both would create a clash in the ManagedCache.

It might (and reasonably ok performance wise) be safe to add something like

int entityHash = sm.getPersistenceCapable().getClass().hashCode();

StateManagerImpl orig = _main.put(entityHash + (29 * sm.getObjectId()), sm);


wdyt?

LieGrue,
strub