On 7/16/07, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> Anyone have any ideas?
Change fieldTypes to be Strings instead, and dematerialize them as needed.
after spending hundreds of hours pursuing other solutions to a similar
issue, i that this would be wise.
<rant>
sounds very similar to the infamous commons logging leak. after a
*lot* of work, Brian Stansberry wrote a custom hashtable
implementation which (after a lot of testing and rewriting) didn't
seem to leak with modern JVMs. we used reference queues and periodic
purging.
IMO the real problem is that the J2EE specification lacks application
life cycle events. i've heard of other leaks (eg when using
reflection) which are hard or impossible to fix. of course, it doesn't
help that the classloader specifications are broke too...
</rant>
- robert
