[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-476) Eventlisteners triggering mutiple times and on null primary keys
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-476?pag...
]
Sanne Grinovero updated HSEARCH-476:
------------------------------------
Attachment: test.log
testAndWorkaround.patch
The patch contains a proof of concept of a possible workaround - i.e. to ignore work
referring to null primary keys - and a test showing the problem. Also some debug
statements are added.
The test.log attachment best illustrates the problem by showing the amount and type of
work which is sent to the workqueue: the duplicates shouldn't be a problem as they
cancel each other out, but the work with null pk causes problems.
Also note the system.out in the end which shows that the null-id works was added to the
index.
Eventlisteners triggering mutiple times and on null primary keys
----------------------------------------------------------------
Key: HSEARCH-476
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-476
Project: Hibernate Search
Issue Type: Bug
Components: engine
Affects Versions: 3.1.0.CR1, 3.1.0.GA, 3.1.1.GA, 3.2.0.Beta1
Reporter: Sanne Grinovero
Assignee: Emmanuel Bernard
Priority: Critical
Attachments: test.log, testAndWorkaround.patch
When persisting a non-trivial (but also not overly complex) entity graph many events are
fired more than once, and several times while the primary key is not yet assigned. This
causes much trouble in the workQueue: it might contain duplicate work, work about entities
with null PK, and possibly even in a work order which results in an inconsistent index.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira