No reason that I can think of. What makes you think the problem is with the IndexSearcher? Maybe it's something else in your code, for instance. Make sure you have the same version of Java on both ends of the call. Also, Java 6 made our RMI calls a lot more stable than even 1.5.
Otis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simpy -- http://www.simpy.com/ - Tag - Search - Share ----- Original Message ---- From: Craig W Conway <[EMAIL PROTECTED]> To: java-user@lucene.apache.org Sent: Wednesday, April 4, 2007 1:25:27 PM Subject: How many Searches is a Searcher Worth? I am using an RMI architecture for calling a remote service which uses an IndexSearcher in its own JVM. I am starting the service with the following provisions for memory allocation and garbage collection: java -server -Xmx1024m -XX:+UseConcMarkSweepGC -XX:+UseParNewGC After about 1000 search calls I start to run out of memory, and I have to close and re-open the IndexSearcher, loosing any cached data and filters... Is there any reason why I shouldn't be able to use my IndexSearcher forever, until I want to close it? Thanks! Craig ____________________________________________________________________________________ Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
