From: | Peter T Mount <peter(at)retep(dot)org(dot)uk> |
---|---|
To: | Gerald Gutierrez <gutz(at)kalador(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Major Memory Leak in PostgreSQL JDBC Driver |
Date: | 2001-04-17 13:19:37 |
Message-ID: | 987513577.3adc42e91ec2a@webmail.retep.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Quoting Gerald Gutierrez <gutz(at)kalador(dot)com>:
>
> At least the 7.1 RC3 driver has a memory leak in that the
> .../jdbc2/PreparedStatement.java class uses Java's ThreadLocal object
> for
> "optimization" reasons. However, Sun's J2SE 1.3 leaks memory whenever
> this
> class is used. Hence, repeated use of the JDBC driver's
> PreparedStatement
> class will cause a major memory leak.
This has already been reported (and there now exists a bug registered with Sun).
As soon as I can I'm going to remove the need for ThreadLocal from the driver.
> that it doesn't have to be instantiated each time (this is the
> optimization), just instantiate the SimpleDateFormat class each time.
> We've
> noticed no performance loss and our application no longer has any
> memory
> leaks.
There was some discussion about this some time ago, and the concensus then was
to limit the number of instanciated SimpleDateFormat's to a minimum.
> Please consider fixing this problem before releasing 7.1.
It should be (assuming I get some spare time between now and then - ie why I'm
a week behind on emails).
Peter
--
Peter Mount peter(at)retep(dot)org(dot)uk
PostgreSQL JDBC Driver: http://www.retep.org.uk/postgres/
RetepPDF PDF library for Java: http://www.retep.org.uk/pdf/
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql-bugs | 2001-04-17 13:26:31 | What's wrong with glibc-devel-2.2 |
Previous Message | pgsql-bugs | 2001-04-17 11:40:02 | JDBC setObject(n,obj) throws exception when obj is null |