Compass Core opens new thread for deleting MarkDeleted rows. when used from a webapp (WebSphere) it is causing connection leaks due to the fact that WAS doesn't (from my knowledge) doesnt allow to commit transactions from the new thread
Created: 20/Nov/07 03:18 PM
Updated: 04/Jan/08 02:52 AM
With 1.2, the scheduler can be disabled (by setting the following setting: compass.engine.indexManagerScheduleInterval to -1). Still, if the scheduler is disabled, the actual scheduled tasks will still need to be executed. Currently, they are not exposed on the SearchEngineIndexManager (which you can get from Compass instance). But it can be casted to LuceneSearchEngineIndexManager, and then call performScheduledTasks.
The fix here moves the performScheduledTasks method from the LuceneSearchEngineIndexManager to SearchEngineIndexManager for simpler usage.
Shay Banon added a comment - 22/Nov/07 02:03 PM A few notes:
With 1.2, the scheduler can be disabled (by setting the following setting: compass.engine.indexManagerScheduleInterval to -1). Still, if the scheduler is disabled, the actual scheduled tasks will still need to be executed. Currently, they are not exposed on the SearchEngineIndexManager (which you can get from Compass instance). But it can be casted to LuceneSearchEngineIndexManager, and then call performScheduledTasks.
The fix here moves the performScheduledTasks method from the LuceneSearchEngineIndexManager to SearchEngineIndexManager for simpler usage.
With 1.2, the scheduler can be disabled (by setting the following setting: compass.engine.indexManagerScheduleInterval to -1). Still, if the scheduler is disabled, the actual scheduled tasks will still need to be executed. Currently, they are not exposed on the SearchEngineIndexManager (which you can get from Compass instance). But it can be casted to LuceneSearchEngineIndexManager, and then call performScheduledTasks.
The fix here moves the performScheduledTasks method from the LuceneSearchEngineIndexManager to SearchEngineIndexManager for simpler usage.