SourceForge.net Logo
Main Overview Wiki Issues Forum Build Fisheye
Issue Details (XML | Word | Printable)

Key: CMP-485
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Shay Banon
Reporter: aravind yarram
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Compass

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
Component/s: Compass::Core
Affects Version/s: 1.2 GA
Fix Version/s: 2.0 M1

Environment: WebSphere 6.1.x, Compass 1.3


 Description  « Hide
Here is the forum link

http://forums.opensymphony.com/thread.jspa?threadID=156052&tstart=0

Provide a configuration flag for disabling the thread spawned for deleting the MarkDelete rows.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
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.


aravind yarram added a comment - 06/Dec/07 10:43 PM
thank you! i will test this with WAS 6.1 once i have my production launch completed!