lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 30628] - Possible Memory leak in Sort
Date Mon, 16 Aug 2004 09:22:09 GMT
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

john@rte.ie changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From john@rte.ie  2004-08-16 09:22 -------
True, in my haste to release the test code, I closed the searcher during the
inner loop instead of during the other loop. I have amended this is the newly
attached file.

My origional code was written as a JSP on Tomcat and tested with Jmeter using 2
threads requesting a simple query and sort. The outer for loop is to mimick the
type of request pattern on the jsp code so that I can compare like with like (ie
500 requests in rapid succession) With sort I get an OutOfMemoryError after 37
requests, without a sort everything works fine for-ever. No other exceptions occur.

---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org


Mime
View raw message