Re: Recommending 3.0.19

How do I turn off JDK agents because I don't explicity turn them on.

> That's not exactly true.
>
> I have not yet verified the claim that a JDK 1.5 version has fixed the
> primitive array introspection/classloader GC bug.
>
> I did not seen any Resin memory leak related to the database pooling.
> With the example you gave in the first bug report, the only memory leak
> was the JDK one.  When the JDK agents were disabled, there was no leak
> at all.
>
> If you have a small test servlet that reproduces this error with JDK
> agents disabled, please send it.
>
> -- Scott
>
>
>> I can get around it by stopping
>> using a datasource and getting a connection to the database using the 
>> good
>> old fashioned java.sql.DriverManager.getConnection but obviously that's
>> quite inefficient.
>>
>>
>>
>>
>> > If the bug really is within Resin, wouldn't everybody using Resin (and
>> > MySQL Connector/J, if I remember things right) see this problem?
>> > What is special about your setup? Has anybody been able to reproduce 
>> > your
>> > problem?
>> >
>> > At 2006-06-20 11:20, you wrote:
>> >>Pity the oom error in the datasource isn't fixed yet, causing my 
>> >>servers
>> >>to crash almost daily.
>> >>
>> >>>So it seems to me, until now our production server ist running and
>> >>>running
>> >>>and running...
>> >>>- no more OutOfMemoryError in perm space (the server is generating
>> >>>permanently new jsp-pages, but the perm space could be cleaned
>> >>>periodically,
>> >>>what shows the garbage collection log)
>> >>>- reliable log rotation
>> >>>- even no other error
>> >>>
>> >>> From our perspective would be given the same recommendation!
>> >>>
>> >>>Keep at it!
>> >>>
>> >>>Olaf Jentsch
>> >>>
>> >>>>-----Original Message-----
>> >>>>From: Mattias Jiderhamn [mailto:[email protected]]
>> >>>>Sent: Tuesday, June 20, 2006 10:38 AM
>> >>>>To: [email protected]; [email protected]
>> >>>>Subject: Recommending 3.0.19
>> >>>>
>> >>>>At 2006-06-14 19:11, Scott Ferguson wrote:
>> >>>> >>That seems a lot more like it by the looks of things. Any
>> >>>>idea on when
>> >>>> >>3.0.20 is going to be released?
>> >>>> >
>> >>>> >Roughly 4-6 weeks.  There are still quite a few bugs to work
>> >>>>through,
>> >>>> >though, so it might change.
>> >>>>
>> >>>>Speaking of this, I must say that after a few weeks with
>> >>>>3.0.19 in production it seems to be really stable. All the
>> >>>>bugs we have seen after the upgrade to 3.0.x have been fixed.
>> >>>> From our perspective, I would recommend anyone using 2.1 and
>> >>>>considering 3.0 to aim for 3.0.19.
>> >>>>
>> >>>>Well done guys!
>> >
>> >
>> >
>>
>>
>
>
>