I think there was a similar thread the dev-list http://thread.gmane.org/gmane.comp.jakarta.ojb.devel/4141
In latest CVS (rc5) we try to avoid use of the "critical methods" in commons-lang. Seems to better now.
regards, Armin
Graham Lounder wrote:
I tried changing the cache options from empty to default with the same results. I can remove the commons-lang-2.0.jar package and put in the commons-lang-1.0.1.jar that comes with OJB and the problem goes away.
Any other ideas? Graham
-----Original Message----- From: Martin Kal�n [mailto:[EMAIL PROTECTED] Sent: December 10, 2003 5:10 PM To: OJB Users List Subject: Re: OutOfMemoryError using commons-lang 2.0 and OJB 1.0rc4
Graham Lounder wrote:
Hello, Since I upgraded commons-lang to version 2.0 (due to the "display" taglib requiring it), OJB (1.0rc4) always throws a OutOfMemoryError when calling getCollectionByQuery() on the defaultPersistenceBroker:
Check if the cache-class in OJB.properties is set to empty or per-broker-cache. This can lead to java.lang.OutOfMemoryError if there are circular auto-retrieve references in the repository. ObjectCacheDefaultImpl can cope with this beacuse of it's static/global cache and would not reveal this mapping problem.
Regards, Martin
-- Martin Kal�n Curalia AB Web: http://www.curalia.se Orrspelsv�gen 2B Mail: [EMAIL PROTECTED] SE-182 79 Stocksund Tel: +46-8-410 064 40
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
