[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-842?pag... ] Hardy Ferentschik reassigned HSEARCH-842: ----------------------------------------- Assignee: Hardy Ferentschik -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-842?pag... ] Johnny B commented on HSEARCH-842: ---------------------------------- It happens on both linux and windows. I first noticed it occurring on our test environment(linux) and did follow up tests locally(windows) for looking for the same symptoms. So I have seen it on both platforms. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-842?pag... ] Hardy Ferentschik updated HSEARCH-842: -------------------------------------- Description: Hi Guys, As already discussed in forum - https://forum.hibernate.org/viewtopic.php?f=9&t=1011938&p=2447638 Basically i notice that the FSMasterDirectoryProvider never releases its file handles even after a full batch index has taken place. Example Test case 1 1. Fresh clean index 2. Batch index takes place, all file handles are closed at the end, nothing is open 3. You can batch index as many times as you want but at the end of each batch index no file handles are open. Test case 2 1. Index exists already, start up application and FSMasterDirectoryProvider opens file handles to existing index 2. Batch index triggered for that index. At the end of the batch index, i notice that the same file file handles are still open as when the app started. This should not be because we have purged the index and carried out a full batch index for it. The index size has now doubled!!! 3. You can carry out as many batch indexes as you want but the very original file handles at start up are always kept open. Test case is attached and forum description gives better insight as to how i carried out the tests Cheers, JB was: Hi Guys, As already discussed in forum https://forum.hibernate.org/viewtopic.php?f=9&t=1011938&p=2447638 Basically i notice that the FSMasterDirectoryProvider never releases its file handles even after a full batch index has taken place. Example Test case 1 1. Fresh clean index 2. Batch index takes place, all file handles are closed at the end, nothing is open 3. You can batch index as many times as you want but at the end of each batch index no file handles are open. Test case 2 1. Index exists already, start up application and FSMasterDirectoryProvider opens file handles to existing index 2. Batch index triggered for that index. At the end of the batch index, i notice that the same file file handles are still open as when the app started. This should not be because we have purged the index and carried out a full batch index for it. The index size has now doubled!!! 3. You can carry out as many batch indexes as you want but the very original file handles at start up are always kept open. Test case is attached and forum description gives better insight as to how i carried out the tests Cheers, JB -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HSEARCH-842?page=com.atlassian.jira.p... ] Sanne Grinovero updated HSEARCH-842: ------------------------------------ Fix Version/s: (was: 3.4.2) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira