Looks like this could be "user error".
In the above code, it looks like objects are getting added to cache locations
"/i/j".
While each objects is removed from "/i/j", the "/i" node remains (leaked by the
user). I added an additional statement:
cache.remove(fqn);
That seems to clean it up, and
Hi all,
I'm running a test program with a simple loop that writes an object to the
cache and then removes it.
As I monitor with JConsole, the heap usage grows and grows and can't be
reclaimed with a garbage collection. Eventually it crashes with an
OutOfMemoryError.
Below is my code.
MemoryLeak
I constructed a test where two JVMs join the same PojoCache cluster.
Each JVM starts one transaction. Here are the two timelines matched up:
| JVM-1JVM-2
|
| --Begin Tx1---
| Modify cachedObj1
| --Begin Tx2---
