DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30628>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30628 Possible Memory leak in Sort [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2004-08-16 09:59 ------- OK, I have just tested using one searcher outside the outer for loop and the code seems to run indefinitely without any issues. So I guess the problem is not quite as simple as I had first thought - as the new test proves that sort does not have a memory leak. I will try use use one instance of IndexSearcher accross all of my JSP sessions and everything should be fine - a question though - (and quite possibly a naive one)....is it always deemed necessary to use one IndexSearcher, would it not be more robust to be able to use a new one for each request? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
