|Memory issue due to hard referenced entities [message #1017891]
||Tue, 12 March 2013 18:05
| Christoph Smaul
Registered: April 2012
we are using eclipselink 2.4.1 (in an JEE application running on JBoss 7.1) and when we started to loadtest our application we experienced OutOfMemoryErrors after a certain while.
A closer look to the heap dump shows that, even if there are no running transactions, an increasing number of entity instances are hard referenced in a path like this:
ServerSession->orderedDescriptors->queryManager->cachedExpressionQueries->..->query->session(RepeatableWriteUnitOfWork)->cloneMapping (see attached screenshot)
There are about 900 instances of RepeatableWriteUnitOfWork, which I assume, should not be the case.
I found a quite similar issue in the bug tracker, but it is fixed since 1.1.2.
So far I could not find a way to disable caching of expression queries to test, if this is the reason for our OOMErrors.
Thanks for your responses.
I managed to set the expression query cache to 0 for all descriptors and this really fixed our memory problem. Of course that's only a workaround, since we would like to benefit from the expression query cache.
So if anyone has a suggestion to deal with this problem in another way, please tell me.
(Size: 181.53KB, Downloaded 112 times)
[Updated on: Wed, 13 March 2013 15:50]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01971 seconds