[eclipselink-dev] Fix for Bug 331098 checked in

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[eclipselink-dev] Fix for Bug 331098 checked in

From: Vikram Bhatia <vikram.jeet.bhatia@xxxxxxxxxx>
Date: Wed, 7 Nov 2012 09:41:58 -0800 (PST)
Delivered-to: eclipselink-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-dev>
List-help: <mailto:eclipselink-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-dev>, <mailto:eclipselink-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-dev>, <mailto:eclipselink-dev-request@eclipse.org?subject=unsubscribe>

Bug 331098 - MemoryLeak in DefaultPersistenceProviderResolver

https://bugs.eclipse.org/bugs/show_bug.cgi?id=331098

· Re-implemented caching strategy of persistence providers in DefaultPersistenceProviderResolver to resolve a memory leak.

Reviewed by: Gordon Yorke

Core & JPA LRG passed with MySQL & Oracle DB.

Fix Checked into EclipseLink 2.5.0. Check-in for 2.4.2 pending.

Prev by Date: Re: [eclipselink-dev] Use of @XmlID/@XmlIDRef when key is in superclass
Next by Date: Re: [eclipselink-dev] Use of @XmlID/@XmlIDRef when key is in superclass
Previous by thread: [eclipselink-dev] 2.4.2 M2 complete...
Next by thread: [eclipselink-dev] EclipseLink Dev meeting cancelled today
Index(es):
- Date
- Thread

Back to the top