]
Emmanuel Bernard resolved HSEARCH-88.
-------------------------------------
Resolution: Fixed
OK I found the issues, my hash based ordering algorithm was flawed when 2 entity types
shared the same underlying index.
It should be fixed now (in SVN)
Unable to update 2 entity types n the same transaction if they share
the same index
-----------------------------------------------------------------------------------
Key: HSEARCH-88
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-88
Project: Hibernate Search
Issue Type: Bug
Components: engine
Affects Versions: 3.0.0.beta3
Environment: Hibernate 3.2.4.sp1, PostGRESQL
Reporter: Charles Chappell
Assignee: Emmanuel Bernard
Fix For: 3.0.0.beta4
Attachments: Login.java, testcase.tar.gz
May be an application server interaction.
Somewhat sporatic, but always in the same places in my code. Basically I had one class
that created an entity exit via NullPointerException, (Database updates were successful)
and a second attempt to read the same data was made, and failed due to this assertion.
The only connection to Hibernate Search is via the Annotations/Runtime, nowhere in this
process did I directly use Hibernate Search.
I'll attempt to produce test code, since this is the simplest case that I've
gotten this assertion failure in.
Application Server is Glassfish, reproducable both on OSX and Solaris 10 Intel.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: