There seems to be a fair number of folks using the jetty with the example app as oppose to using Solr with their own appserver. So I think it is best to use a stable version of Jetty instead of the beta. If no one objects, I can go ahead and take care of this.
Bill On 5/4/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
I verified that Tomcat 5.5.17 doesn't experience this problem. -Yonik On 5/4/06, Yonik Seeley <[EMAIL PROTECTED]> wrote: > On 5/3/06, Yonik Seeley <[EMAIL PROTECTED]> wrote: > > I just tried sending in 100,000 deletes and it didn't cause a problem: > > the memory grew from 22M to 30M. > > > > Random thought: perhaps it has something to do with how you are > > sending your requests? > > Yep, I was able to reproduce a memory problem w/ Jetty on Linux when > using non-persistent connections (closed after each request). The > same 100,000 deletes blew up the JVM to 1GB heap. > > So this looks like it could be a Jetty problem (shame on me for using a beta). > I'm still not quite sure what changed in Solr that could make it > appear in later version and not in earlier versions though... the > version of Jetty is the same.
