[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: ------------------------------------------- This is using Seam, I am in a Tx, I'm pretty sure... In 3.1 it looks the same though: # I call flush() # the FullTextEntityListener is called for my insertions # The work is added to the BatchedQueueingProcessor.add() # Since my batchSize is > 0 and < than workQueu.size() the DocumentBuilder is invoked # This loads lazy-loaded collections in flush() I'm not sure what would be a workaround, since my insert events cannot be notified to HS before flush is called so calling flushToIndexes before flush is not useful. Note that when doing batch inserts I don't think HS indexing should be deferred before commit, but simply after flush. Unless it could be asynchronous and done outside of my transaction entirely ;) -- 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