[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-178) Out of transaction work causes collection lazy loading to throw AssertionFailure

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-178?pag... ] Stephane Epardaud commented on HSEARCH-178: ------------------------------------------- I see from fisheye there are several changes to fix this: it looks like the processing is delayed until after flushing. Unfortunately I'm using Seam which isn't up to date with all the HS 3.1 requirements for hibernate so I can't upgrade, but I've already backported FullTextSession.flushToIndexes() to 3.0 which I'm using for my batch insertion: while(...){ // save some entities session.flush(); // this one first since it triggers the HS event listener session.flushToIndexes(); session.clear(); } This breaks in HS but only when HS's batch_size is smaller than my flush frequency (this is when flush will trigger the insert listener which will process the work instead of batching it for later) which happens easily with @ContainedIn since the queue goes up faster than the number of objects I'm inserting. I'll try backporting your commits and see if that fixes my problem. -- 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