tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: release 6.0.21
Date Mon, 21 Dec 2009 11:04:59 GMT
On 21/12/2009 10:53, Rainer Frey wrote:
> On Monday 21 December 2009 11:12:12 jean-frederic clere wrote:
>> Hi,
>> Later today I will tag and go for the release, make sure all the patches
>> you want to see in are committed :-)
> Well, I'm no committer and I don't understand the relevant code well  enough 
> to possibly create a patch, but I hoped that someone would take a look at 
> issue before a 
> release is made (This issue was introduced by changes after 6.0.20, and Mark 
> Thomas told me on the users list to create a bugzilla entry for that).

I hadn't forgotten that one - I just hadn't got around to looking at it.
I have a few ideas about what might be going on.

My guess is that you are relying on the auto-driver registration
process. It is this process that triggers the memory leak so Tomcat now
forcibly de-registers any drivers the JVM auto-registers.

If you get a chance before I get to it later today, try using a context
listener to register and de-register the driver when your app starts and
stops and let us know how you get on.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message