[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-222?pag... ] Sanne Grinovero reassigned HSEARCH-222: --------------------------------------- Assignee: (was: Sanne Grinovero) fine, but I unassign it from myself as I have overestimated my free time :-( I'm still willing to to it, just I can't guarantee a patch soon. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-222?pag... ] Sanne Grinovero updated HSEARCH-222: ------------------------------------ Description: As we update an entity by deleting it from index by using an IndexReader, and afterwards we reinsert it using an IndexWriter, there is a point in time in the middle were no DPlock is held on the Directory, At this moment a ReaderProvider could (re)open the index and all searches performed on this IndexReader will not find the entity at all. We should use a Read/Write Lock on DP instead of the current ReentrantLock to use a write lock during index updates and avoid creating a bottleneck for different threads needing a searcher. was: As we update an entity by deleting it from index by using a database, and afterwards we reinsert it using an IndexWriter, there is a point in time in the middle were no DPlock is held on the Directory, At this moment a ReaderProvider could (re)open the index and all searches performed on this IndexReader will not find the entity at all. We should use a Read/Write Lock on DP instead of the current ReentrantLock to use a write lock during index updates and avoid creating a bottleneck for different threads needing a searcher. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-222?pag... ] Emmanuel Bernard commented on HSEARCH-222: ------------------------------------------ It sounds that this problem is solved, right? Can I close it Sanne? -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-222?pag... ] Sanne Grinovero resolved HSEARCH-222. ------------------------------------- Resolution: Fixed The issue is solved for all transactional work, for batch works it would be suboptimal so in this case it could show up. -- 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