[
https://issues.apache.org/jira/browse/SOLR-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-1735.
----------------------------
Resolution: Fixed
Fix Version/s: (was: 4.0)
3.5
4.0-ALPHA
Unless I'm missing something, this issue was actually resolved by the commit in
LUCENE-2822 that added the TimeLimitingCollector.getGlobalCounter() (and made
Solr start using it).
Not sure why this issue was left open.
(If i'm wrong, and this still affects 3.6 and 4.0-BETA, then someone please
re-open with more details)
> shut down TimeLimitedCollection timer thread on application unload
> ------------------------------------------------------------------
>
> Key: SOLR-1735
> URL: https://issues.apache.org/jira/browse/SOLR-1735
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3, 1.4
> Reporter: Chris Darroch
> Assignee: Simon Willnauer
> Fix For: 4.0-ALPHA, 3.5
>
> Attachments: SOLR-1735-1_3.patch
>
>
> As described in https://issues.apache.org/jira/browse/LUCENE-2237, shutting
> down the timer thread created by Lucene's TimeLimitedCollector allows Tomcat
> or another application server to cleanly unload solr.war (or any application
> using Lucene, for that matter).
> I'm attaching two patches for Solr 1.3 which use the patch provided in
> LUCENE-2237 to shut down the timer thread when a new servlet context listener
> for the solr.war application is informed the application is about to be
> unloaded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
