Derby 10.9.1.0
I am battling an OutOfMemory error that periodically occurs. I believe it is
triggered by a problem in my code that keeps a set of locks for too long and
another thread from another client interaction fails to acquire the locks that
it needs and triggers an lock timeout error.
I have been capturing heap dumps and I have one in which
ContextManager.cleanupOnError is active and the errorStringBuilder's buffer is
835MB. The stack trace to the call to ContextManager.cleanupOnError is also
strange to me as it is being called:
Java.util.TimerThread
Java.lang.ThreadLocal$ThreadLocalMapEntry[16]
java.lang.ThreadLocal$ThreadLocalMap$Entry
org.apache.derb.iapi.services.context.ContextManager
I tried finding out this call hierarchy to maybe determine more about the
problem but so far, no luck.
I am also a little concerned by the "forever" loop within the
ContextManager.cleanupOnError. Is it possible that this loop might never
terminate?
Thanks in advance.
Brett
________________________________
Canoga Perkins
20600 Prairie Street
Chatsworth, CA 91311
(818) 718-6300
This e-mail and any attached document(s) is confidential and is intended only
for the review of the party to whom it is addressed. If you have received this
transmission in error, please notify the sender immediately and discard the
original message and any attachment(s).
