[ https://issues.apache.org/jira/browse/SOLR-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-2285. ---------------------------- Resolution: Fixed trunk: Committed revision 1048886. 3x: Committed revision 1048890. > excess SolrEventListeners created and then thrown away > ------------------------------------------------------ > > Key: SOLR-2285 > URL: https://issues.apache.org/jira/browse/SOLR-2285 > Project: Solr > Issue Type: Bug > Affects Versions: 1.4, 1.4.1 > Reporter: Hoss Man > Assignee: Hoss Man > Fix For: 3.1, 4.0 > > Attachments: SOLR-2285.patch > > > As noted by Jørgen Trosby on the solr mailing list (subj: "SolrEventListeners > are instantiated twice", "Mon, 11 Oct 2010 18:11:07 +0200") there is a > problem with how SolrEventListeners are being created and initialized > the bug is two fold: > * the UpdatedHandler and the SolrCore both independently loop over all > SolrEventListeners looking for the two classes of use cases they directly > care about (postCommit/postOptimize vs newSearcher/firstSearcher) -- in both > cases they construct every declared listener even if it is not a type they > care about > * even when UpdatedHandler is finding a postCommit it cared about, it throws > it away and constructing it again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org