I was able to produce an OutOfMemoryError using Yonik's python script with
Jetty 6.
I was not able to do so with Jetty 5.1.11RC0, the latest stable version. So
that's the
version of Jetty with which I will downgrade the Solr example app to.
Bill
On 5/5/06, Erik Hatcher <[EMAIL PROTECTED]> wrote:
Along these lines, locally I've been using the latest stable version
of Jetty and it has worked fine, but I did see an "out of memory"
exception the other day but have not seen it since so I'm not sure
what caused it.
Moving to Tomcat, as long as we can configure it to be as lightweight
as possible, is quite fine to me as well.
Erik
On May 5, 2006, at 12:12 PM, Bill Au wrote:
> 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.
>>
