This content has been marked as final. Show 2 replies
if you have a reproducible testcase I suggest you file a bug. This is the only way to get it resolved.
I have the same problem. The partial solution was to increase heap space and lower the session timeout in the web.xml, cause this collection seems to be associated with the user http session. As soon as the session was expired, the GC will be able to free this memory space, lowering the chances of jvm crash. The original cause have not been discovered yet.
xtanto, which tool did you use to get the list of objects at the server ? (bytes used and percentage of heap occupation)